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 rhettinger
Recipients gvanrossum, matthiastroffaes, rhettinger, skip.montanaro
Date 2009-08-15.05:37:48
SpamBayes Score 0.00672242
Marked as misclassified No
Message-id <1250314670.05.0.455625207697.issue6695@psf.upfronthosting.co.za>
In-reply-to
Content
Does anyone here know why GC calls the free_xxx functions?  ISTM, they
cannot be involved in cycles.  Free lists are kept by container objects
to speed-up allocation.  Having GC call the free_xxx just slows down the
GC process and all the subsequent set/list/tuple allocations until the
free lists are built-up again.  IMO, the free_xxx functions should only
be called during atexit or by an explicit call from the user perhaps,
sys.clear_freelists() or somesuch.
History
Date User Action Args
2009-08-15 05:37:50rhettingersetrecipients: + rhettinger, gvanrossum, skip.montanaro, matthiastroffaes
2009-08-15 05:37:50rhettingersetmessageid: <1250314670.05.0.455625207697.issue6695@psf.upfronthosting.co.za>
2009-08-15 05:37:49rhettingerlinkissue6695 messages
2009-08-15 05:37:48rhettingercreate