This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author neologix
Recipients flox, kaifeng, neologix, pitrou
Date 2011-04-19.17:26:46
SpamBayes Score 3.90125e-06
Marked as misclassified No
Message-id <>
> BTW, after utilize lxml instead of ElementTree, such phenomenon of increasing memory usage disappeared.

If you looked at the link I posted, you'll see that lxml had some similar issues and solved it by calling malloc_trim systematically when freeing memory.
It could also be heap fragmentation, though.

To go further, it'd be nice if you could provide the output of
valgrind --tool=memcheck --leak-check=full --suppressions=Misc/valgrind-python.supp python <test script>
after uncommenting relevant lines in Misc/valgrind-python.supp (see ).
It will either confirm a memory leak or malloc issue (I still favour the later).

By the way, does

while True:

lead to a constant memory usage increase ?
Date User Action Args
2011-04-19 17:26:47neologixsetrecipients: + neologix, pitrou, flox, kaifeng
2011-04-19 17:26:47neologixsetmessageid: <>
2011-04-19 17:26:47neologixlinkissue11849 messages
2011-04-19 17:26:46neologixcreate