Dieter, I most definitely use Python 2.1.3 ... I however AM using 2.5.0 ... A bit old I know, I'm about to start working on upgrading when 2.6.1 comes out ... Are there specific bugs in 2.5.0 that could be causing this behavior? I vaguely recall looking at the Change Log and Collector, but not finding much about any kind of memory leak ... For now I AM going to try and remove any use I make of REQUEST.set, see if that helps ... Thanks! J.F. -----Original Message----- From: Dieter Maurer [mailto:dieter@handshake.de] Sent: Wednesday, December 18, 2002 6:10 PM To: Jean-Francois.Doyon@CCRS.NRCan.gc.ca Cc: zope@zope.org; jo@meder.de Subject: RE: [Zope] My Zope is leaking memory ... Still no luck. (PythonSc ript bug) Jean-Francois.Doyon@CCRS.NRCan.gc.ca writes:

Well, I tried to look at the PythonScript issue, and it looks like there's definitely something "odd" going on here ...

As Jo suggested, I tried "cleaning out" my variables at the end of my Python Scripts ... I didn't do this for ALL of them though, just the most used ones, which actually aren't CMF related (Search Engine is one) ...

And now what happens is the memory grows, BUT, at some point, the Zope process DIES with a SIG11 (Aieeee!), restarts, and voila, of course, the memory is clean. Are you sure, you use Python 2.1.3 and at least Zope 2.4.4 or 2.5.1?

If you do, I would be very astonished when explicit clearing of Python script variables were still necessary. (We do not clear any Python script variables and do not see disturbing leaks). Dieter