[issue4373] Reference leaks in Python 3.0rc3

Christian Heimes <[EMAIL PROTECTED]> added the comment: Second fix applied in r67382 -- resolution: -> fixed status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> ___

[issue4373] Reference leaks in Python 3.0rc3

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: Applied pickle-leak2.patch in 67381. ___ Python tracker <[EMAIL PROTECTED]> ___ ___ P

[issue4373] Reference leaks in Python 3.0rc3

Brett Cannon <[EMAIL PROTECTED]> added the comment: Amaury's patch for pickle looks fine to me. -- nosy: +brett.cannon ___ Python tracker <[EMAIL PROTECTED]> ___ __

[issue4373] Reference leaks in Python 3.0rc3

Changes by Barry A. Warsaw <[EMAIL PROTECTED]>: -- priority: deferred blocker -> release blocker ___ Python tracker <[EMAIL PROTECTED]> ___

[issue4373] Reference leaks in Python 3.0rc3

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: The problem is that on Windows (and cygwin) you cannot unlink a .pyd that is currently loaded in memory. I tried to use ctypes and call FreeLibrary. Now the .pyd can be removed, but the interpreter crashes when it comes to free the modu

[issue4373] Reference leaks in Python 3.0rc3

Christian Heimes <[EMAIL PROTECTED]> added the comment: Good analysis Amaury! The new patch for build ext uses a single temp dir. -- nosy: +loewis Added file: http://bugs.python.org/file12092/issue4373_build_ext2.patch ___ Python tracker <[EMAIL PROTE

[issue4373] Reference leaks in Python 3.0rc3

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: The refleak in test_pickle comes from unpickler_read(). The attached patch corrects it. Added file: http://bugs.python.org/file12090/pickle-leak2.patch ___ Python tracker <[EMAIL PROTECTED]>

[issue4373] Reference leaks in Python 3.0rc3

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: I have studied this some time ago. The xx module comes each time from a different file (in a directory created with tempfile.mkdtemp). Every instance of the module creates a new entry in the static "extensions" dictionary in Python/impo

[issue4373] Reference leaks in Python 3.0rc3

Christian Heimes <[EMAIL PROTECTED]> added the comment: This simple patch doesn't load the 'xx' module more than once in ref leak tests. The problem may also be caused by the xxmodule itself. Somebody should give it a proper review :) -- keywords: +patch Added file: http://bugs.python.o

[issue4373] Reference leaks in Python 3.0rc3

Christian Heimes <[EMAIL PROTECTED]> added the comment: distutils.tests.test_build_ext leaks the references. I think it's related to the xx module and totally harmless. ___ Python tracker <[EMAIL PROTECTED]> _

[issue4373] Reference leaks in Python 3.0rc3

Christian Heimes <[EMAIL PROTECTED]> added the comment: Only distutils and pickle seem to have real leaks. $ ./python Lib/test/regrtest.py -R:15: test_multiprocessing test_multiprocessing beginning 20 repetitions 12345678901234567890 1 test OK. [124096 refs] $ ./python Lib/

[issue4373] Reference leaks in Python 3.0rc3

New submission from Christian Heimes <[EMAIL PROTECTED]>: A refleak test of r67311 py3k shows several leaks: test_distutils leaked [142, 142, 142, 142] references, sum=568 test_httpservers leaked [0, 0, 0, 217] references, sum=217 test_multiprocessing leaked [0, 0, 24, 0] references, sum=24 test