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 Vipul-Cariappa, serhiy.storchaka, vstinner
Date 2020-11-29.14:53:14
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1606661594.28.0.40293952055.issue42502@roundup.psfhosted.org>
In-reply-to
Content
1 KiB is too low for Python. The interpreter itself needs more than 10 MiB to start, and more if it imports some modules. I suppose that the limit set affect only new requests for memory from OS, but Python already have some free memory reserved in the memory pool.

With larger limit you can get more reliable data. Note that get_traced_memory() counts only dynamically allocated memory, it does not count static memory, stack memory and memory reserved for the memory pool.
History
Date User Action Args
2020-11-29 14:53:14serhiy.storchakasetrecipients: + serhiy.storchaka, vstinner, Vipul-Cariappa
2020-11-29 14:53:14serhiy.storchakasetmessageid: <1606661594.28.0.40293952055.issue42502@roundup.psfhosted.org>
2020-11-29 14:53:14serhiy.storchakalinkissue42502 messages
2020-11-29 14:53:14serhiy.storchakacreate