[Python-Dev] possible memory leak on windows (valgrind report) (original) (raw)
Reinhold Birkenfeld reinhold-birkenfeld-nospam at wolke7.net
Mon Sep 19 20:36:19 CEST 2005
- Previous message: [Python-Dev] possible memory leak on windows (valgrind report)
- Next message: [Python-Dev] possible memory leak on windows (valgrind report)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Neal Norwitz wrote:
I ran 2.4.x through valgrind and found two small problems on Linux that have been fixed. There may be some other issues which could benefit from more eyes (small, probably one time memory leaks). The entire run is here:
http://python.org/valgrind-2.4.2.out (I need to write a lot more suppression rules for gentoo.) I think I see a memory leak in win32startfile. Since I don't run windows I can't test it. filepath should be allocated with the et flag to PyArgsParseTuple(), but it wasn't freed without this patch. Does this make sense? See the attached patch.
Applied the patch, this was my fault.
Reinhold
-- Mail address is perfectly valid!
- Previous message: [Python-Dev] possible memory leak on windows (valgrind report)
- Next message: [Python-Dev] possible memory leak on windows (valgrind report)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]