[issue21435] Segfault with cyclic reference and asyncio.Future
Antoine Pitrou
report at bugs.python.org
Wed May 7 10:39:31 CEST 2014
Antoine Pitrou added the comment:
> The new info: its (the list object's) gc_refs also changed from
> GC_TENTATIVELY_UNREACHABLE to GC_UNTRACKED, That the object became
> untracked is wholly consistent with that its gc_next became NULL but
> not its gc_prev.
Could that be the trashcan mecanism?
----------
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue21435>
_______________________________________
More information about the Python-bugs-list
mailing list