[issue6741] Garbage collector release method

2019-10-22 Thread STINNER Victor


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

___
Python tracker 

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



[issue6741] Garbage collector release method

2013-03-18 Thread Satshabad Khalsa

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. 

Unfortunately the test is not failing for the right reasons and I can't figure 
out why.

--
nosy: +Satshabad.Khalsa
Added file: http://bugs.python.org/file29463/patch

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



[issue6741] Garbage collector release method

2010-07-10 Thread Terry J. Reedy

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
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue6741] Garbage collector release method

2009-08-21 Thread Lev

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 rep...@bugs.python.org
http://bugs.python.org/issue6741
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue6741] Garbage collector release method

2009-08-20 Thread Lev

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 in GC list without 
reference count checking, and call this method at the end of py_Finalize
() function. I think, that it will help to avoid memory leaks after 
calling py_Finalize() function.

--
components: Interpreter Core
messages: 91772
nosy: gardster
severity: normal
status: open
title: Garbage collector release method
type: feature request
versions: Python 2.6

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



[issue6741] Garbage collector release method

2009-08-20 Thread Martin v . Löwis

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
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com