Josh Rosenberg added the comment:

The fact that it's resolved by PyGC_Collect indicates there is a reference 
cycle somewhere. PyGC_Collect is just looking for cyclic garbage and breaking 
the cycles so it can be cleaned; it would happen eventually unless GC was 
explicitly disabled or the process exited before the next implicit GC 
invocation, so it means this bug is really about timing (and possibly cycles 
we'd prefer to avoid), not reference leaks.

nosy: +josh.r

Python tracker <>
Python-bugs-list mailing list

Reply via email to