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 | methane, serhiy.storchaka, vstinner |
| Date | 2018年10月24日.12:19:05 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1540383545.33.0.788709270274.issue35053@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
A little bit of history. I opened a bug 2 years ago but I closed it (lack of interest): https://github.com/vstinner/pytracemalloc/issues/2 I rewrote tracemalloc between version 0.9 and 1.0. In tracemalloc 0.9, there was an API to track free lists. Here is the code to handle "alloc" and "free" of an object inside a freelist: https://github.com/vstinner/pytracemalloc/blob/a2b2616fc73cd5ce0ea45d1b68a490e0fc52ccc8/_tracemalloc.c#L291-L337 My PR 10063 has a more correct and efficient implementation: * It keeps the trace alive when the object moves into the free list to report the real memory usage of Python: the free lists consumes memory * It writes directly into the hash table entry rather than remove/add frequently the trace, it should be more efficient |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2018年10月24日 12:19:05 | vstinner | set | recipients: + vstinner, methane, serhiy.storchaka |
| 2018年10月24日 12:19:05 | vstinner | set | messageid: <1540383545.33.0.788709270274.issue35053@psf.upfronthosting.co.za> |
| 2018年10月24日 12:19:05 | vstinner | link | issue35053 messages |
| 2018年10月24日 12:19:05 | vstinner | create | |