diff options
| author | Tim Peters <tim.peters@gmail.com> | 2003-11-12 20:43:28 (GMT) |
|---|---|---|
| committer | Tim Peters <tim.peters@gmail.com> | 2003-11-12 20:43:28 (GMT) |
| commit | add09b4149b17afa30aa042dbb718b9d9ec741c3 (patch) | |
| tree | e3d9f2501d6143ff2d27a50a7d93674c99dde7cd /Misc/NEWS | |
| parent | 045f1de57ed524d5dbaab92fea8eabc59b33d6f2 (diff) | |
| download | cpython-add09b4149b17afa30aa042dbb718b9d9ec741c3.zip cpython-add09b4149b17afa30aa042dbb718b9d9ec741c3.tar.gz cpython-add09b4149b17afa30aa042dbb718b9d9ec741c3.tar.bz2 | |
SF bug 840829: weakref callbacks and gc corrupt memory.
subtype_dealloc(): This left the dying object exposed to gc, so that
if cyclic gc triggered during the weakref callback, gc tried to delete
the dying object a second time. That's a disaster. subtype_dealloc()
had a (I hope!) unique problem here, as every normal dealloc routine
untracks the object (from gc) before fiddling with weakrefs etc. But
subtype_dealloc has obscure technical reasons for re-registering the
dying object with gc (already explained in a large comment block at
the bottom of the function).
The fix amounts to simply refraining from reregistering the dying object
with gc until after the weakref callback (if any) has been called.
This is a critical bug (hard to predict, and causes seemingly random
memory corruption when it occurs). I'll backport it to 2.3 later.
Diffstat (limited to 'Misc/NEWS')
| -rw-r--r-- | Misc/NEWS | 6 |
1 files changed, 6 insertions, 0 deletions
@@ -12,6 +12,12 @@ What's New in Python 2.4 alpha 1? Core and builtins ----------------- +- Critical bugfix, for SF bug 840829: if cyclic garbage collection + happened to occur during a weakref callback for a new-style class + instance, subtle memory corruption was the result (in a release build; + in a debug build, a segfault occurred reliably very soon after). + This has been repaired. + - Added a reversed() builtin function that returns a reverse iterator over a sequence. |