Re: memory allocation failed!

• Date: Sun, 9 Jun 1996 17:32:10 PDT
• From:
  Pavel Curtis <pavel@parc.xerox.com>
• Cc: moo-cows@parc.xerox.com
• In-reply-to: Justin Harris's message of "Sun, 09 Jun 1996 14:12:30 PDT" <Pine.LNX.3.91.960609170205.736A-100000@gomer.mlink.net>

Justin Harris writes:
> This happened is the middle of a checkpoint...the DB is a little bit more 
> than 10 megs, running on HP/UX, with 1.8.0p5 and FUP. This isn't the first
> time this has happened...since I know we're not the only MOO with this 
> problem maybe there is some sort of bug? Maybe in the checkpointing process?

Maybe, instead, you're really running out of memory...  You say this is
happening during a checkpoint; at that time, the server has split into two
copies and so it using up twice as much memory as usual.  Do you know how much
swap space is allocated on this machine?  As a first step, maybe you should
increase it.

	Pavel

• memory allocation failed!
• From: Justin Harris <rebel@gomer.mlink.net>

• Prev: memory allocation failed!
• Next: memory leak in latest lambdaMOO
• Index: MOO-cows
• Thread: MOO-cows