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 methane
Recipients barry, benjamin.peterson, davin, lukasz.langa, methane, nascheme, rhettinger, tim.peters, vstinner, yselivanov
Date 2017-09-24.07:51:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
AFAIK, Python shutdown process calls full GC.

Don't touching permanent generation makes shutdown faster.
On the other hand, there are some downside:

* Some object may be not freed while shutdown.  It looks like "leak" for application embedding Python interpreter.
* Some __del__ methods may be not be called.

Of course, GC permanent generation while shutdown doesn't make sense.
gc.freeze() is used for sharing more memory pages.  Shutdown process
shouldn't unshare them.

So I think these notable downside should be documented.
Date User Action Args
2017-09-24 07:51:31methanesetrecipients: + methane, tim.peters, barry, nascheme, rhettinger, vstinner, benjamin.peterson, lukasz.langa, yselivanov, davin
2017-09-24 07:51:31methanesetmessageid: <>
2017-09-24 07:51:31methanelinkissue31558 messages
2017-09-24 07:51:30methanecreate