[issue18884] python-2.7.5-r3: 40 bytes in 1 blocks are definitely lost

2013-08-30 Thread Tim Peters
Tim Peters added the comment: Now you have something to show the matplotlib folks - although they're not likely to get excited about leaking 40 bytes. There is nothing Python can do about this. matplotlib is responsible for free'ing the memory matplotlib allocates, just as Python is responsib

[issue18884] python-2.7.5-r3: 40 bytes in 1 blocks are definitely lost

2013-08-30 Thread Martin Mokrejs
Changes by Martin Mokrejs : Added file: http://bugs.python.org/file31523/valgrind_python275_without-pymalloc.txt ___ Python tracker ___ ___ P

[issue18884] python-2.7.5-r3: 40 bytes in 1 blocks are definitely lost

2013-08-30 Thread Martin Mokrejs
Martin Mokrejs added the comment: Of course I did recompile matplotlib to use the recompiled python with debug ABI. I just don't understand why if something is not leaded why a memleak has to happen. Anyway, now my application using the recompiled matplotlib baffled this through valgrind as w

[issue18884] python-2.7.5-r3: 40 bytes in 1 blocks are definitely lost

2013-08-30 Thread Tim Peters
Tim Peters added the comment: The matplotlib people won't care about this one either. matplotlib allocated the memory, and the error message at the end says it's _trying_ to call _PyMem_DebugFree (which may well be trying to release the memory), but the binaries aren't compatible: _PyMem_Deb

[issue18884] python-2.7.5-r3: 40 bytes in 1 blocks are definitely lost

2013-08-30 Thread STINNER Victor
STINNER Victor added the comment: According to traces, the leak does not come from Python but matplotlib. Please report the issue to matplotlib bug tracker. -- resolution: -> invalid status: open -> closed ___ Python tracker

[issue18884] python-2.7.5-r3: 40 bytes in 1 blocks are definitely lost

2013-08-30 Thread Martin Mokrejs
Martin Mokrejs added the comment: Why do you think so? My point is that this happens when import fails. But python is at fault and should handle import errors. -- ___ Python tracker ___

[issue18884] python-2.7.5-r3: 40 bytes in 1 blocks are definitely lost

2013-08-30 Thread Antoine Pitrou
Changes by Antoine Pitrou : -- priority: normal -> low ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://m

[issue18884] python-2.7.5-r3: 40 bytes in 1 blocks are definitely lost

2013-08-30 Thread Ezio Melotti
Changes by Ezio Melotti : -- nosy: +haypo, pitrou, skrah type: -> resource usage ___ Python tracker ___ ___ Python-bugs-list mailing

[issue18884] python-2.7.5-r3: 40 bytes in 1 blocks are definitely lost

2013-08-30 Thread Martin Mokrejs
New submission from Martin Mokrejs: It is not important why I had in this moment matplotlib not in sync with python itself whcih was configure using --with-pydebug ... but here I just want to show that maybe you do not test for memleaks using valgrind on import errors (maybe include such testc