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 christian.heimes, gvanrossum, kumaraditya, miss-islington, sobolevn, vstinner
Date 2022-02-23.18:02:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1645639364.1.0.587735064281.issue46430@roundup.psfhosted.org>
In-reply-to
Content
> Presumably the leak is imaginary

Well, you can check with your favorite memory debugger like Valgrind if you don't trust Python internal memory debugger :-)

Not leaking memory at exit matters when Python is embedded in an application.

I don't think that it's related to the error handling which is stripped in release mode.
History
Date User Action Args
2022-02-23 18:02:44vstinnersetrecipients: + vstinner, gvanrossum, christian.heimes, miss-islington, sobolevn, kumaraditya
2022-02-23 18:02:44vstinnersetmessageid: <1645639364.1.0.587735064281.issue46430@roundup.psfhosted.org>
2022-02-23 18:02:44vstinnerlinkissue46430 messages
2022-02-23 18:02:44vstinnercreate