[issue13089] parsetok.c: memory leak

2012-02-16 Thread Stefan Krah
Stefan Krah added the comment: Yes, that's basically what I did, but using the latest revision I cannot reproduce the parsetok leak either. The atexit leak is an old friend (#11826), so I think we can close this one for now. -- resolution: -> out of date stage: needs patch -> committe

[issue13089] parsetok.c: memory leak

2012-02-15 Thread Meador Inge
Meador Inge added the comment: Stefan, how did you reproduce this? I tried: 1. Uncommenting '#define Py_USING_MEMORY_DEBUGGER' in 'Objects/obmalloc.c'. 2. Configuring with './configure --without-pymalloc'. 3. Running 'valgrind --tool=memcheck --log-file=leaks.txt --leak-check=full --sup

[issue13089] parsetok.c: memory leak

2012-02-14 Thread Antoine Pitrou
Changes by Antoine Pitrou : -- nosy: +benjamin.peterson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://

[issue13089] parsetok.c: memory leak

2011-11-19 Thread Petri Lehtinen
Changes by Petri Lehtinen : -- nosy: +petri.lehtinen ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue13089] parsetok.c: memory leak

2011-10-02 Thread Meador Inge
Changes by Meador Inge : -- nosy: +meador.inge ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue13089] parsetok.c: memory leak

2011-10-02 Thread Stefan Krah
New submission from Stefan Krah : Seen in test_mailbox: ==31621== 6 bytes in 2 blocks are definitely lost in loss record 27 of 10,370 ==31621==at 0x4C2154B: malloc (vg_replace_malloc.c:236) ==31621==by 0x5271A5: parsetok (parsetok.c:179) ==31621==by 0x526E8A: PyParser_ParseStringFlag