Note that this is likely caused by some sort of brainbending circular
reference problem that might be helped by Python 2.X's cyclic garbage
collector.
Well, will also try out python 2.x then... (btw. are all 2.x python versions
working without problems with Zope? Don't want to get
Hi!
It looks like you're leaking requests. This is often the consequence of
setting an attribute on the REQUEST object which is aquisition wrapped.
For instance:
REQUEST.adtmldoc = REQUEST['PARENTS'][0]
When requests leak, references to all the objects referenced within the
request
Note that this is likely caused by some sort of brainbending circular
reference problem that might be helped by Python 2.X's cyclic garbage
collector.
Well, will also try out python 2.x then... (btw. are all 2.x python versions
working without problems with Zope? Don't want to get a new
Chris McDonough wrote:
Note that this is likely caused by some sort of brainbending circular
reference problem that might be helped by Python 2.X's cyclic garbage
collector.
Well, will also try out python 2.x then... (btw. are all 2.x python versions
working without problems with
Hi there!
I got another problem with my Zope server and that seems to be
a memory hole..
I am using Zope 2.3.2 with Python 1.5.2 now on SuSE 7.0 (this
seems to solve the hanging problem, which appeared on 7.1) and
I use Python Script, ZSQL methods, ZMySQLDA and ZPatterns.
Now using top I see
Hi Christian,
It looks like you're leaking requests. This is often the consequence of
setting an attribute on the REQUEST object which is aquisition wrapped.
For instance:
REQUEST.adtmldoc = REQUEST['PARENTS'][0]
When requests leak, references to all the objects referenced within the
request
