[Pymerase-devel] [ pymerase-Bugs-1256258 ] DBAPI Memory Leak

[SourceForge.net <no...@so...>]

Bugs item #1256258, was opened at 2005-08-10 16:19
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=505345&aid=1256258&group_id=63836

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Output: CreateDBAPI
Group: v0.2
Status: Open
Resolution: None
Priority: 9
Submitted By: Brandon King (kingb)
Assigned to: Brandon King (kingb)
Summary: DBAPI Memory Leak

Initial Comment:
Pymerase DBAPI has a memory leak where if you have two
DBAPI objects (lets say A and B) and you call
A.appendB(B) and then call del on B, it won't destory
B... This actually shouldn't happen, because if your
still holding on to A, then A should still hold on to
B. But if you call del on   A and B, neither will
actually be deleted because this have references
eachother and them selves.

The solution for is too fold... First using a weakref
from each object to itself head in the right direction.
Second, a function will need to be implemented such as
B._destroySelf() to tell it you want to remove it from
memory (which is needed if you commit a large number of
Bs and you're try to free up some memory by not holding
on to all previously commited B objects). This function
_destroySelf() would tell B to go to all associated
objects and remove any referrences to itself. Then you
would call del B to really remove the object from memory.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=505345&aid=1256258&group_id=63836