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 thehesiod
Recipients asvetlov, methane, pitrou, thehesiod, vstinner
Date 2018-05-22.16:38:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1527007127.98.0.682650639539.issue33565@psf.upfronthosting.co.za>
In-reply-to
Content
that's not going to affect http://pytracemalloc.readthedocs.io/api.html#get_traced_memory.  There is no filter for that :)

as to your sum that's exactly what my original callstack lists:
21 memory blocks: 4.7 KiB

this means 21 blocks were not released, and in this case leaked because nothing should be held onto after the first iteration (creating the initial connector in the connection pool.  In the head object case that's going to be a new connector per iteration, however the old one should go away.
History
Date User Action Args
2018-05-22 16:38:48thehesiodsetrecipients: + thehesiod, pitrou, vstinner, asvetlov, methane
2018-05-22 16:38:47thehesiodsetmessageid: <1527007127.98.0.682650639539.issue33565@psf.upfronthosting.co.za>
2018-05-22 16:38:47thehesiodlinkissue33565 messages
2018-05-22 16:38:47thehesiodcreate