This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Title: help fix memory usage or leak - edgewall trac 0.11 blocked ...
Type: Stage:
Components: Versions: Python 2.5
Status: closed Resolution: not a bug
Dependencies: Superseder:
Assigned To: Nosy List: ThurnerRupert, christian.heimes
Priority: normal Keywords:

Created on 2008-01-19 11:04 by ThurnerRupert, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (2)
msg60147 - (view) Author: (ThurnerRupert) Date: 2008-01-19 11:04
how could one find a memory problem in python. edgewall trac 0.11 
seems blocked for such a problem, where nobody had a really helpful 
idea for nearly three weeks.

msg60151 - (view) Author: Christian Heimes (christian.heimes) * (Python committer) Date: 2008-01-19 11:12
You should take the problem to the general Python mailing list. Sorry,
but the bug tracker is the wrong place.

Some hints:

Do you have classes with a __del__ method which may create reference
cycles? The GC can't break cycles when a __del__ method is involved.

Are you keeping references to tracebacks, exception objects (except
Exception, err) or frames (sys._getframe())?
Date User Action Args
2022-04-11 14:56:29adminsetgithub: 46179
2008-01-19 11:12:28christian.heimessetstatus: open -> closed
resolution: not a bug
messages: + msg60151
nosy: + christian.heimes
2008-01-19 11:04:01ThurnerRupertcreate