Fix various potential memory misuses #160
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
g_free() of libglib is not interchangeable with free() of libc, if
glib is built with ENABLE_MEM_PROFILE or ENABLE_MEM_CHECK defined,
so memory allocated with g_malloc() family should be released with
g_free() rather than free(), as
https://mail.gnome.org/archives/gtk-list/2000-July/msg00002.html
pointed out.
the return value of xmlnode_to_str() should be released with
g_free(), otherwise it is leaked.
Signed-off-by: HardenedVault [email protected]