[Zope-dev] memory error on BSDi [Q]

Christopher Petrilli petrilli@digicool.com
Mon, 10 Jan 2000 10:21:31 -0500


On 1/8/00 5:32 PM, Bruno Mattarollo at brunomadv@ciudad.com.ar wrote:

> Hello...
> 
> I had the following traceback on a Zope-2.0.1 that we are using on a BSDi with
> a virtual kernel.
> 
> I had problems compiling it but finally it did... It has been running with
> lots of problems since then and now I have seen this traceback ...
> 
> chicos: {6} % Unhandled exception in thread:
> Traceback (innermost last):
> File 
> "/usr/home/chicos/usr/local/ZopeChicosNet/ZServer/PubCore/ZServerPublisher.py"
> , line 95, in __init__
> response=response)
> File 
> "/usr/home/chicos/usr/local/ZopeChicosNet/lib/python/ZPublisher/Publish.py",
> line 224, in publish_module
> response.exception()
> File 
> "/usr/home/chicos/usr/local/ZopeChicosNet/lib/python/ZPublisher/HTTPResponse.p
> y", line 630, in exception
> elif lower(strip(b))[:6]=='<html>' or lower(strip(b))[:14]=='<!doctype html':
> MemoryError
> 
> 
> Does anyone knows when a MemoryError raise appears? Is it hardware error? If
> so, I will send this to our hosting rep.

You might want to read the Python library reference, but the real meaning
is:

Raised when an operation runs out of memory but the situation may still be
rescued (by deleting some objects). The associated value is a string
indicating what kind of (internal) operation ran out of memory. Note that
because of the underlying memory management architecture (C's malloc()
function), the interpreter may not always be able to completely recover from
this situation; it nevertheless raises an exception so that a stack
traceback can be printed, in case a run-away program was the cause.

What this makes me think is that you have simply run out of memory, either
on your machine, or more likely, your process...

Chris
-- 
| Christopher Petrilli        Python Powered        Digital Creations, Inc.
| petrilli@digicool.com                             http://www.digicool.com