[issue14761] Memleak in import.c load_source_module()

2012-05-09 Thread Antoine Pitrou
Antoine Pitrou added the comment: Fixed, thank you! -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed versions: +Python 3.2 ___ Python tracker __

[issue14761] Memleak in import.c load_source_module()

2012-05-09 Thread Roundup Robot
Roundup Robot added the comment: New changeset 9de4d85e4197 by Antoine Pitrou in branch '3.2': Issue #14761: Fix potential leak on an error case in the import machinery. http://hg.python.org/cpython/rev/9de4d85e4197 New changeset 840cb46d0395 by Antoine Pitrou in branch 'default': Null merge fo

[issue14761] Memleak in import.c load_source_module()

2012-05-09 Thread Roundup Robot
Roundup Robot added the comment: New changeset a775fc27f469 by Antoine Pitrou in branch '2.7': Issue #14761: Fix potential leak on an error case in the import machinery. http://hg.python.org/cpython/rev/a775fc27f469 -- nosy: +python-dev ___ Python tr

[issue14761] Memleak in import.c load_source_module()

2012-05-09 Thread Damien Cassou
Damien Cassou added the comment: @pitrou I just checked Python-2.7.3 and the tip of the mercurial repository. It's not in the latter at least. -- ___ Python tracker ___ ___

[issue14761] Memleak in import.c load_source_module()

2012-05-09 Thread Antoine Pitrou
Antoine Pitrou added the comment: Is it 2.7-only? -- nosy: +brett.cannon, ncoghlan, pitrou stage: -> patch review type: -> resource usage ___ Python tracker ___ __

[issue14761] Memleak in import.c load_source_module()

2012-05-09 Thread Damien Cassou
New submission from Damien Cassou : In load_source_module() function from import.c, it looks like Py_DECREF is not called where it should be. Please find attached a patch that fixes the leak. This bug has been found using Coccinelle (http://coccinelle.lip6.fr/) using a semantic patch (similar