STINNER Victor added the comment:
That's basically a duplicate of bpo-1635741.
--
nosy: +vstinner
resolution: -> duplicate
stage: test needed -> resolved
status: open -> closed
superseder: -> Py_Finalize() doesn't clear all Python objects at exit
Satshabad Khalsa added the comment:
This is a test that is supposed to run c that creates two objects, cross
references them with embedded python DECREF's the objects. Then it asserts that
after Py_fini is called, they have no more references because the gc should
have collected them.
Changes by Terry J. Reedy tjre...@udel.edu:
--
stage: - unit test needed
versions: +Python 3.2 -Python 2.6
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6741
___
Lev lgards...@gmail.com added the comment:
I,m trying to develop this patch now, but I'm facing the challenge
(wrong ref_count or list corruption in dict objects). If I can solve
it, I publish patch here.
--
___
Python tracker
New submission from Lev lgards...@gmail.com:
WinCRT debug detects several memory leaks after calling py_Initialize
(); py_Finalize(); functions. Most of them are garbage collector
visible python's objects. I suggest to create release method in
garbage collector which will distruct all objects
Martin v. Löwis mar...@v.loewis.de added the comment:
Can you propose a patch?
--
nosy: +loewis
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6741
___
