|Issue 36:||Memory leaks|
|2 people starred this issue and may be notified of changes.||Back to list|
What steps will reproduce the problem? run the tixidemo under valgrind What is the expected output? What do you see instead? Several memory leaks and invalid reads occur. Please use labels and text to provide additional information. Culprit seems to be the mallocs in tixiUtils::strip_dirname. We have to make sure to free the strings on document close and on remalloc.
Aug 7, 2012
Following leaks have been identified: - leak when saving document - leak when inserting node at specified index - leak when creating/opening document All these leaks should be fixed in revision 112 In addition, a tixiCleanup() function was created, that calls xmlCleanupParser - more or less cosmetic but helps to silence valgrind.
Aug 8, 2012
Removed a leak in tixiGetArray in revision 113
Nov 21, 2012
We have lots of leaks in xpathFunctions.c. Reason is that libxml2 allocates objects (e.g. xmlXPathObjectPtr) which should be freed by the user but we don't do it. One Example is xpathFunctions.c:139 . The object is never freed. Running valgrind over some unit tests reveals these problems.
|► Sign in to add a comment|