On 26 May 2009, at 18:10, David Van Couvering wrote:
Yes, it does happen after resume, this seems to be the culprit based
on all
the responses. Good as new after the processes terminate, you say?
OK,
I'll give that a shot.
Might be worth adding to the FAQ?
Nah, it should be fixed. -- I think it is the timers we use for the
stats API
get fired (which causes a process spawn) after wakeup. So for each
second while sleeping you get a process. When you hit 32k processes
(the Erlang VM default setting), you get the error message.
A custom timer module that skips expired timers will help here. Any
takers? :)
Cheers
Jan
--
Thanks,
David
On Tue, May 26, 2009 at 1:40 AM, Jan Lehnardt <j...@apache.org> wrote:
On 26 May 2009, at 06:05, David Van Couvering wrote:
Hi, all. I am using v0.9.0 on MacOS, and I have deployed some
couchapps to
it. Whenever I leave it running for a while (say overnight), I
come back
and
it is spitting out "=== ERROR REPORT === too many processes" over
and over
again and I have to restart couchdb.
Any ideas what could be causing this? Googling didn't show me
very much
to
You say it runs overnight. Do you also let your system sleep at
some point?
I have a suspicion there's a relation to having a sleeping Mac OS
X. In any
case, the errors should be harmless. In my experience, CouchDB is
good
as new after all the processes terminate.
Cheers
Jan
--
--
David W. Van Couvering
http://www.linkedin.com/in/davidvc
http://davidvancouvering.blogspot.com
http://twitter.com/dcouvering
