[issue8258] Multiple Python Interpreter Memory Leak

2010-07-21 Thread Amaury Forgeot d'Arc
Amaury Forgeot d'Arc amaur...@gmail.com added the comment: It's actually the same issue as issue1635741 -- nosy: +amaury.forgeotdarc resolution: - duplicate status: open - closed superseder: - Interpreter seems to leak references after finalization

[issue8258] Multiple Python Interpreter Memory Leak

2010-07-20 Thread Mark Lawrence
Changes by Mark Lawrence breamore...@yahoo.co.uk: -- nosy: +brian.curtin, tim.golden stage: - needs patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8258 ___

[issue8258] Multiple Python Interpreter Memory Leak

2010-03-29 Thread William
New submission from William william.le...@mastek.com: Context: I am embedding Python into a Windows based C++ application, where a new Python interpreter (using Py_NewInterpreter) is created for each user who connects to the system. When the user logs off, the function Py_EndInterpreter is