You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The patch adds a new test and a new executable. The executable calls
Py_Initialze() and Py_Finalize() multiple times in a row. The test also
shows that Python looses about 35 references in each round.
I'm not sure what the purpose of this test is. When would it pass, when
would it fail? I don't think it is a bug if a
Py_Initialize()/Py_Finalize() cycle loses references.
I'm not sure what the purpose of this test is. When would it pass, when
would it fail? I don't think it is a bug if a
Py_Initialize()/Py_Finalize() cycle loses references.
Today my attempts to fix some reference leaks related to sys.flags and
sys.float_info caused the test to fail. A single init/final cycle worked
but the second cycle broke.
The test also shows an issue in Python 3.0. The double linked reference
list is broken:
Activity
tiran commentedon Jan 30, 2008
The patch adds a new test and a new executable. The executable calls
Py_Initialze() and Py_Finalize() multiple times in a row. The test also
shows that Python looses about 35 references in each round.
loewis commentedon Jan 30, 2008
I'm not sure what the purpose of this test is. When would it pass, when
would it fail? I don't think it is a bug if a
Py_Initialize()/Py_Finalize() cycle loses references.
tiran commentedon Jan 30, 2008
Martin v. Löwis wrote:
Today my attempts to fix some reference leaks related to sys.flags and
sys.float_info caused the test to fail. A single init/final cycle worked
but the second cycle broke.
The test also shows an issue in Python 3.0. The double linked reference
list is broken:
pitrou commentedon Jan 31, 2008
Perhaps ROUNDS, CAUSE_SEGFAULT and VERBOSE could be command-line rather
than compile-time options?
tiran commentedon Jan 31, 2008
I like to keep the test as simple as possible.
Here is a new file that shows Python crashes in the third Py_Finalize().
tiran commentedon Jan 31, 2008
If fixed the problem with multiple reinitialization in r60477. It took
me quite some time to find the right spot.
pitrou commentedon Mar 14, 2009
This is still a good idea.
BreamoreBoy commentedon Sep 20, 2010
Quote msg83564 "This is still a good idea.", in which case shouldn't someone push this forward, failing that close as out of date?
pitrou commentedon Sep 20, 2010
Just because someone doesn't "push this forward" doesn't mean it's out of date.
pitrou commentedon Jan 15, 2011
See also bpo-10914.
tiran commentedon Nov 26, 2012
Antoine, is the test still required? bpo-10914 has introduced tests for the subinterpreter.
pitrou commentedon Nov 26, 2012
Ah, funny. I ended up doing the same thing as you without remembering about it!