[issue1635741] Interpreter seems to leak references after finalization

2015-08-17 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 FlagsUserPtr UserSize - state
00db14434690 030a   [00]   00db144346c003074 - (busy)
7ffc55628b04 ntdll!RtlpCallInterceptRoutine+0x0040
7ffc555f9f36 ntdll!RtlAllocateHeap+0x00079836
7ffc2a60c4da ucrtbased!calloc_base+0x123a
7ffc2a60c27d ucrtbased!calloc_base+0x0fdd
7ffc2a60f34f ucrtbased!malloc_dbg+0x002f
7ffc2a60fdde ucrtbased!malloc+0x001e
5a5e6ef9 python36_d!_PyMem_RawMalloc+0x0029
5a5e78c7 python36_d!_PyMem_DebugAlloc+0x0087
5a5e5e6f python36_d!_PyMem_DebugMalloc+0x001f
5a5e7230 python36_d!PyMem_Malloc+0x0030
5a582047 python36_d!new_keys_object+0x0077
5a57f7c5 python36_d!dictresize+0x0085
5a57a4b2 python36_d!PyDict_Merge+0x0112
5a57bf33 python36_d!PyDict_Update+0x0023
5a75fb1d python36_d!PyImport_Cleanup+0x045d
5a778f9e python36_d!Py_Finalize+0x005e

--
nosy: +Alex Budovski

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1635741] Interpreter seems to leak references after finalization

2014-02-03 Thread Mark Lawrence 

Changes by Mark Lawrence :


--
nosy:  -BreamoreBoy

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1635741] Interpreter seems to leak references after finalization

2013-04-20 Thread Martin Morrison 

Changes by Martin Morrison :


--
nosy: +isoschiz, pconnell

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1635741] Interpreter seems to leak references after finalization

2011-03-31 Thread Tim Lesher 

Changes by Tim Lesher :


--
nosy: +tlesher

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1635741] Interpreter seems to leak references after finalization

2011-03-13 Thread Santoso Wijaya 

Changes by Santoso Wijaya :


--
nosy: +santa4nt

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1635741] Interpreter seems to leak references after finalization

2011-03-12 Thread Ray.Allen 

Ray.Allen  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]


This seems to be a known bug that Py_Finalize() doesn't free all objects 
according doc 
http://docs.python.org/dev/c-api/init.html?highlight=py_finalize#Py_Finalize

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1635741] Interpreter seems to leak references after finalization

2011-02-13 Thread Ray.Allen 

Changes by Ray.Allen :


--
nosy: +ysj.ray

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1635741] Interpreter seems to leak references after finalization

2010-07-21 Thread Amaury Forgeot d'Arc 

Amaury Forgeot d'Arc  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 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1635741] Interpreter seems to leak references after finalization

2010-07-20 Thread Mark Lawrence 

Mark Lawrence  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

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1635741] Interpreter seems to leak references after finalization

2009-03-30 Thread Daniel Diniz 

Changes by Daniel Diniz :


--
stage:  -> test needed
type:  -> resource usage
versions: +Python 2.6, Python 3.0 -Python 2.5

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com