[issue1635741] Interpreter seems to leak references after finalization

2015-08-18 Thread Alex Budovski
Alex Budovski added the comment: Interestingly enough, some of the leaked memory came from the finalize routine itself! Here's one example: 0:004 !heap -p -a 0x00DB144346F0 address 00db144346f0 found in _HEAP @ db0cae HEAP_ENTRY Size Prev Flags

[issue1635741] Interpreter seems to leak references after finalization

2014-02-03 Thread Mark Lawrence
Changes by Mark Lawrence breamore...@yahoo.co.uk: -- nosy: -BreamoreBoy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1635741 ___ ___

[issue1635741] Interpreter seems to leak references after finalization

2013-04-20 Thread Martin Morrison
Changes by Martin Morrison m...@ensoft.co.uk: -- nosy: +isoschiz, pconnell ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1635741 ___ ___

[issue1635741] Interpreter seems to leak references after finalization

2011-03-31 Thread Tim Lesher
Changes by Tim Lesher tles...@gmail.com: -- nosy: +tlesher ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1635741 ___ ___ Python-bugs-list mailing

[issue1635741] Interpreter seems to leak references after finalization

2011-03-13 Thread Santoso Wijaya
Changes by Santoso Wijaya santoso.wij...@gmail.com: -- nosy: +santa4nt ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1635741 ___ ___

[issue1635741] Interpreter seems to leak references after finalization

2011-03-12 Thread Ray.Allen
Ray.Allen ysj@gmail.com added the comment: Does the title of this issue accurately reflect the current status of the Python interpreter? Yes, here is the running result on current 3.3 latest code: [37182 refs] [39415 refs] [41607 refs] [43799 refs] [45991 refs] [48183 refs] [50375 refs]

[issue1635741] Interpreter seems to leak references after finalization

2011-02-13 Thread Ray.Allen
Changes by Ray.Allen ysj@gmail.com: -- nosy: +ysj.ray ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1635741 ___ ___ Python-bugs-list mailing

[issue1635741] Interpreter seems to leak references after finalization

2010-07-21 Thread Amaury Forgeot d'Arc
Amaury Forgeot d'Arc amaur...@gmail.com added the comment: Yes, some objects are not cleaned in finalization. This is not a problem in usual cases though, when the interpreter is started only once. -- nosy: +amaury.forgeotdarc ___ Python tracker

[issue1635741] Interpreter seems to leak references after finalization

2010-07-20 Thread Mark Lawrence
Mark Lawrence breamore...@yahoo.co.uk added the comment: Does the title of this issue accurately reflect the current status of the Python interpreter? -- nosy: +BreamoreBoy versions: +Python 2.7, Python 3.1, Python 3.2 -Python 2.6, Python 3.0 ___

[issue1635741] Interpreter seems to leak references after finalization

2009-03-30 Thread Daniel Diniz
Changes by Daniel Diniz aja...@gmail.com: -- stage: - test needed type: - resource usage versions: +Python 2.6, Python 3.0 -Python 2.5 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1635741