[issue23769] valgrind reports leaks for test_zipimport

STINNER Victor added the comment: > valgrind reports leaks for test_zipimport It's not strictly a memory leak: running the same code multiple time doesn't leak memory. It's just that Python allocates memory once and never releases it (doesn't releast it at exit). --- leak4.py: Updated and

[issue23769] valgrind reports leaks for test_zipimport

Serhiy Storchaka added the comment: zipimport has been rewritten in pure Python (issue25711). -- nosy: +serhiy.storchaka ___ Python tracker ___ ___

[issue23769] valgrind reports leaks for test_zipimport

Robert Kuska added the comment: I tried leak2.py with valgrind, I've uncommented the lines you mentioned. > $ valgrind python3 leak2.py > >

[issue23769] valgrind reports leaks for test_zipimport

STINNER Victor added the comment: When calling gc.collect() after each test, I don't see any leak anymore. doTest() has a small leak: it prepends a path to sys.path, but it never removes it. Try attached leak2.py: it displays something like +254 kB. Uncomment the two following lines and the o

[issue23769] valgrind reports leaks for test_zipimport

Robert Kuska added the comment: Summary for valgrind python3 test_zipimport.py ==18608== ==18608== HEAP SUMMARY: ==18608== in use at exit: 1,596,390 bytes in 11,536 blocks ==18608== total heap usage: 343,849 allocs, 332,313 frees, 59,355,776 bytes allocated ==18608== ==18608== LEAK SUMM

[issue23769] valgrind reports leaks for test_zipimport

Changes by Robert Kuska : Added file: http://bugs.python.org/file38673/report ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubsc

[issue23769] valgrind reports leaks for test_zipimport

New submission from Robert Kuska: Leaks happen only when both testDoctestFile and testDoctestSuite are run. Run with Python 3.4.2 and 3.4.1 with same result. I have extracted those two tests into `leak.py` (attached). > $ valgrind --suppressions=/../cpython/Misc/valgrind-python.supp python3 >