----- Original Message ----- From: "Chris Withers" <[EMAIL PROTECTED]>
To: "Jonathan" <[EMAIL PROTECTED]>
Cc: "zope list user" <zope@zope.org>
Sent: Thursday, August 09, 2007 1:24 PM
Subject: Re: [Zope] debugging memory exhaustion


Jonathan wrote:

Of course, it'd be lovely if you could actually specify an upper memory bound for a particular request to use, and/or Zope as a whole, but these kinds of things always seem to stall at the development stage :-(

If you're running on a linux machine you could look into the ulimit command to limit the process memory utilization, which may allow you to see what it happening.

Er no, that would just exacerbate the problem.
The machine itself is functional, just with low memory.
Zope is throwing MemoryErrors because the OS won't give it anymore.
ulimit'ing zope would just make those MemoryErrors come sooner...

In your original post you said:

"Of course, it'd be lovely if you could actually specify an upper memory
bound for a particular request to use, and/or Zope as a whole"

If your server is still alive and Zope is throwing memory errors, then Zope has hit its specified upper memory limit. What do you want Zope to do at this point?

Jonathan


_______________________________________________
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope-dev )

Reply via email to