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.

classification
Title: Integrate tracemalloc into regrtest refleak hunting
Type: enhancement Stage: needs patch
Components: Tests Versions: Python 3.4, Python 3.5
process
Status: closed Resolution: duplicate
Dependencies: Superseder: test.regrtest: use tracemalloc to detect memory leaks?
View: 19816
Assigned To: Nosy List: ezio.melotti, ncoghlan, neologix, vstinner, zach.ware
Priority: normal Keywords:

Created on 2014-08-13 06:42 by ncoghlan, last changed 2022-04-11 14:58 by admin. This issue is now closed.

Messages (3)
msg225257 - (view) Author: Alyssa Coghlan (ncoghlan) * (Python committer) Date: 2014-08-13 06:42
Trying to debug issue #22166, I realised it would be nice if there was an easy way to use tracemalloc to get a clear idea of *what's* leaking when regrtest -R reports a refleak.

For that specific issue, I'm just trying to hack something together as a learning experience, but it would be good to have something more sophisticated built in to regrtest.
msg225258 - (view) Author: Ezio Melotti (ezio.melotti) * (Python committer) Date: 2014-08-13 06:44
Isn't this the same as #19816?
msg225265 - (view) Author: Alyssa Coghlan (ncoghlan) * (Python committer) Date: 2014-08-13 07:47
Indeed it is - I should have checked if there was an existing issue.
History
Date User Action Args
2022-04-11 14:58:06adminsetgithub: 66386
2014-08-13 07:47:09ncoghlansetstatus: open -> closed
superseder: test.regrtest: use tracemalloc to detect memory leaks?
resolution: duplicate
messages: + msg225265
2014-08-13 06:44:09ezio.melottisetnosy: + ezio.melotti
messages: + msg225258
2014-08-13 06:42:55ncoghlancreate