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 2007-06-18 14:43 by ocean-city, last changed 2022-04-11 14:56 by admin. This issue is now closed.
Files | ||||
---|---|---|---|---|
File name | Uploaded | Description | Edit | |
archive.zip | ocean-city, 2007-06-18 14:43 | |||
archive.zip | ocean-city, 2007-06-18 17:48 | version2 | ||
test_leak.py | ajaksu2, 2009-04-06 09:39 | Test thread-related ref leaks | ||
experimental.patch | ajaksu2, 2009-04-06 09:41 | Help diagnosing thread-related ref leaks |
History | |||
---|---|---|---|
Date | User | Action | Args |
2022-04-11 14:56:25 | admin | set | github: 45106 |
2009-10-31 03:32:20 | ocean-city | set | status: open -> closed resolution: duplicate superseder: memory leaks in py3k messages: + msg94741 |
2009-05-10 21:01:50 | pitrou | set | nosy:
+ pitrou messages: + msg87547 |
2009-04-06 09:41:31 | ajaksu2 | set | files:
+ experimental.patch title: Investigated ref leak report related to thread(regrtest.py - -> Investigated ref leak report related to thread regrtest.py |
2009-04-06 09:39:55 | ajaksu2 | set | files:
+ test_leak.py type: resource usage keywords: + patch nosy: + ajaksu2 messages: + msg85622 stage: patch review |
2007-06-18 14:43:50 | ocean-city | create |