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 berker.peksag, methane, minrk, vstinner
Date 2016-09-14.13:10:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1473858630.44.0.824867412907.issue28147@psf.upfronthosting.co.za>
In-reply-to
Content
The CPython test suite uses a counter on memory allocations. Please add an unit test which triggers the memory leak, but you don't need many iterations. One iteartion should be enough to be catched by the unit test. Try: ./python -m test -R 3:3 test_dict.

The memory allocation counter:
https://docs.python.org/dev/library/sys.html#sys.getallocatedblocks

Note: The tracemalloc module can also be used to track memory leak, but it's harder to use it to write unit tests because Python uses a lot of internal caches and tracemalloc really tracks every single bytes.
History
Date User Action Args
2016-09-14 13:10:30vstinnersetrecipients: + vstinner, methane, berker.peksag, minrk
2016-09-14 13:10:30vstinnersetmessageid: <1473858630.44.0.824867412907.issue28147@psf.upfronthosting.co.za>
2016-09-14 13:10:30vstinnerlinkissue28147 messages
2016-09-14 13:10:30vstinnercreate