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 tim.peters
Date 2004-10-28.01:58:53
SpamBayes Score
Marked as misclassified
Oh oh.  It's that time of year again.  I'm sure the 
attached ( can be simplified, perhaps down 
to two objects and one thread.  As is, I *think* it 
demonstrates that invoking a weakref callback can do 
fatal damage, not necessarily because of what the 
callback does, but because simply calling it while gc is 
running can allow other threads to run during gc too, 
and resurrect a piece of cyclic trash T that's already 
been tp_clear()'ed, via invoking a still-living weakref to 

If so, this isn't new in 2.4.  It's a real problem since is what's left of ZODB 3.4a1 <wink>.
Date User Action Args
2007-08-23 14:27:06adminlinkissue1055820 messages
2007-08-23 14:27:06admincreate