➜
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.
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: Nick Coghlan (ncoghlan) *  |
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) * |
Date: 2014-08-13 06:44 | |
Isn't this the same as #19816? |
|||
| msg225265 - (view) | Author: Nick Coghlan (ncoghlan) * |
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:06 | admin | set | github: 66386 |
| 2014-08-13 07:47:09 | ncoghlan | set | status: open -> closed superseder: test.regrtest: use tracemalloc to detect memory leaks? resolution: duplicate messages: + msg225265 |
| 2014-08-13 06:44:09 | ezio.melotti | set | nosy:
+ ezio.melotti messages: + msg225258 |
| 2014-08-13 06:42:55 | ncoghlan | create | |