➜

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 progval
Recipients Valentin.Lorentz, pitrou, progval, tacocat, vstinner
Date 2016-11-29.16:23:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <99dddaae-4460-11a3-f4ce-c4654d18977d@gmail.com>
In-reply-to <1480435981.36.0.812998475683.issue28663@psf.upfronthosting.co.za>
Content 
I dumped tracemalloc's statistics just before the assert False. Line
numbers are unchanged (I added code on existing lines).

Result as attachement.

On 29/11/2016 17:13, STINNER Victor wrote:
> STINNER Victor added the comment:
>
> It's very hard to estimate the water high-mark for memory because the memory includes different things: read-only memory, mmap() on files, read-only memory pages shared between multiple processes for libraries, etc.
>
> I suggest to use the tracemalloc module to have a better idea of the memory usage of the memory directly allocated by Python.
>
> ----------
> nosy: +haypo
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue28663>
> _______________________________________
Files
File name Uploaded
rlimit_tracemalloc.txt progval, 2016-11-29.16:23:20
History
Date User Action Args
2016-11-29 16:23:28progvalsetrecipients: + progval, pitrou, vstinner, Valentin.Lorentz, tacocat
2016-11-29 16:23:27progvallinkissue28663 messages
2016-11-29 16:23:27progvalcreate