Its not easy. Try looking at LeakFinder which Shane recently released, this is more fun than the standard: watch the refcounts in debug, and hit urls till you see an increase. Cheers. -- Andy McKay. ----- Original Message ----- From: "Ron Bickers" <rbickers-dated-995323719.270b67@logicetc.com> To: "Andy McKay" <andym@activestate.com>; "Dieter Maurer" <dieter@handshake.de>; "Ron Bickers" <rbickers-dated-995298075.870779@logicetc.com> Cc: "Zope List" <zope@zope.org> Sent: Monday, July 09, 2001 3:48 PM Subject: RE: [Zope] Refcount question (memory leak)
-----Original Message----- From: Andy McKay [mailto:andym@ActiveState.com]
Hm, there was a SQLAlias memory leak in earlier versions of Zope. Maybe, the problem is not yet finally fixed...
It is, that has been fixed - I checked. Leaking the Acquistion Wrapper shows that the actual REQUEST is being leaked.
I'm using SQLSession with MySQL and there seems to be some correlation with setting up a new session variable and those two leaking refounts going up. That's just with my half hour testing, so I'm really just guessing.
I upgraded MySQL-python and ZMySQLDA to the latest to see what happens. Could those even be the culprit? Is there a simple/practical way to find the leak?
Thanks! _______________________
Ron Bickers Logic Etc, Inc.
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )