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 alexandre.vassalotti, neologix, pitrou, serhiy.storchaka, tim.peters, vstinner
Date 2014-05-23.09:26:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1400837204.7.0.773938094899.issue21556@psf.upfronthosting.co.za>
In-reply-to
Content
"Ah, so this means CF's patch will make the pickle memotable invisible to tracemalloc?"

Currently, _Py_hashtabe uses PyMem_RawMalloc and PyMem_RawFree by default (realloc is not needed, we need to keep the previous buckets on rehash). Using _Py_hashtable_new_full, you can choose a different memory allocator.

Hum, wait. tracemalloc uses trace PyMem_RawMalloc and PyMem_RawFree. In fact, tracemalloc ignores reentrant calls to the memory allocator. So now I don't remember exactly why I chose a custom hash table implementation :-) Maybe because Python dict requires Python objects with reference counter, use the garbage collector, etc.
History
Date User Action Args
2014-05-23 09:26:44vstinnersetrecipients: + vstinner, tim.peters, pitrou, alexandre.vassalotti, neologix, serhiy.storchaka
2014-05-23 09:26:44vstinnersetmessageid: <1400837204.7.0.773938094899.issue21556@psf.upfronthosting.co.za>
2014-05-23 09:26:44vstinnerlinkissue21556 messages
2014-05-23 09:26:43vstinnercreate