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 serhiy.storchaka
Recipients erlendaasland, serhiy.storchaka, vstinner, xiang.zhang
Date 2021-04-16.07:41:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1618558861.64.0.131814469698.issue35056@roundup.psfhosted.org>
In-reply-to
Content
No, I did not mean using msize() or something like. Since memory is managed outside of Python, we have no a list of allocated blocks.

I meant that we can get the total memory used by the Python process (using OS-specific methods) and compare it between iterations. If it continues to grow, there is a leak. It perhaps is not able to detect small leaks (less than the page size), but large leaks are more important.
History
Date User Action Args
2021-04-16 07:41:01serhiy.storchakasetrecipients: + serhiy.storchaka, vstinner, xiang.zhang, erlendaasland
2021-04-16 07:41:01serhiy.storchakasetmessageid: <1618558861.64.0.131814469698.issue35056@roundup.psfhosted.org>
2021-04-16 07:41:01serhiy.storchakalinkissue35056 messages
2021-04-16 07:41:00serhiy.storchakacreate