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 vstinner
Recipients methane, serhiy.storchaka, vstinner
Date 2019-06-18.13:12:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1560863530.02.0.403023527376.issue37329@roundup.psfhosted.org>
In-reply-to
Content
> The best would be to explicitly release all memory at exit, but I don't think that it's worth it in Python 2.7 (...)

Python 2.7 "leaks" a lot of memory at exit...

==18497==      possibly lost: 5,665,418 bytes in 27,453 blocks
==18497==    still reachable: 8,530,840 bytes in 57,856 blocks

... but the operating system releases the memory anyway when the process exit. Technically, it's not a major issue unless you embed Python into an application. But again, it's Python 2.7: I suggest to focus efforts in the master branch.
History
Date User Action Args
2019-06-18 13:12:10vstinnersetrecipients: + vstinner, methane, serhiy.storchaka
2019-06-18 13:12:10vstinnersetmessageid: <1560863530.02.0.403023527376.issue37329@roundup.psfhosted.org>
2019-06-18 13:12:10vstinnerlinkissue37329 messages
2019-06-18 13:12:09vstinnercreate