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 asvetlov, methane, pitrou, thehesiod, vstinner
Date 2018-05-22.13:59:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1526997543.63.0.682650639539.issue33565@psf.upfronthosting.co.za>
In-reply-to
Content
A memory leak is when each iteration adds a fixed number of bytes of the memory: I'm talking about tracemalloc.get_traced_memory()[0] value. For example, if you compare the total traced memory between your iteration 30 and iteration 20, you get a value 10N. If you compare iteration 100 and 20, I would expect the value 80N. Is it the case?

You can get the number of allocated bytes from a snapshot using:

>>> sum(trace.size for trace in snapshot.traces)
2620350
History
Date User Action Args
2018-05-22 13:59:03vstinnersetrecipients: + vstinner, pitrou, asvetlov, methane, thehesiod
2018-05-22 13:59:03vstinnersetmessageid: <1526997543.63.0.682650639539.issue33565@psf.upfronthosting.co.za>
2018-05-22 13:59:03vstinnerlinkissue33565 messages
2018-05-22 13:59:03vstinnercreate