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 darrenr
Recipients LambertDW, benjamin.peterson, darrenr
Date 2008-12-31.22:52:00
SpamBayes Score 0.00133907
Marked as misclassified No
Message-id <1230763922.49.0.265820190452.issue4794@psf.upfronthosting.co.za>
In-reply-to
Content
A 'stop-the-world' garbage collector that periodically released the GIL
could be run in a second thread, allowing the main thread to break in
and do some processing. However the nature of a stop-the-world collector
means that it probably would not easily be able to deal with changes
made by other threads in the middle of the collect.

My concern is that the Python process blocks and is unresponsive due to
garbage collection for periods of time that are not acceptable for
realtime interactive applications. Are there any plans to add an
incremental collector to Python?
History
Date User Action Args
2008-12-31 22:52:03darrenrsetrecipients: + darrenr, benjamin.peterson, LambertDW
2008-12-31 22:52:02darrenrsetmessageid: <1230763922.49.0.265820190452.issue4794@psf.upfronthosting.co.za>
2008-12-31 22:52:01darrenrlinkissue4794 messages
2008-12-31 22:52:00darrenrcreate