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.

Author dyoo
Recipients
Date 2002-04-04.07:14:06
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
Logged In: YES 
user_id=49843

Martin is right: I need to retract part of my bug-report: I
just remembered that any classes that have a __del__ method
aren't automatically cleaned  by a gc.collect().  I
triggered a pseudo-Heisenbug during my testing.

After removing the __del__ method from my test class and by
using parseString() instead of feed(), I've verified that
the XML parsing isn't the source of my memory leak.  (Test
file test_memory_leak_2.py included.)

However, after further investigation, I did find the true
source of my problems.. in MySQLdb:

http://sourceforge.net/tracker/index.php?func=detail&aid=536624&group_id=22307&atid=374932

Thank you again for looking into this.
History
Date User Action Args
2007-08-23 14:00:09adminlinkissue535474 messages
2007-08-23 14:00:09admincreate