-
Notifications
You must be signed in to change notification settings - Fork 163
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Finally, added the XML weak_ptr memory leak fix
- Loading branch information
DennisPopovDn
committed
Aug 22, 2015
1 parent
b1bf8ab
commit 28e90bb
Showing
4 changed files
with
58 additions
and
23 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
28e90bb
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello @DennisPopovDn I have included your non-contentious / obvious memory leak fixes (i.e.
xmlFree()
onchar*
and namespace string) in a feature branch we are currently working on:efc71c2
Thank you!
I have also incorporated your slightly more "controversial"
weak_ptr
-related changes, behind an#ifdef
preprocessor directive which is deactivated by default:a33c979
I say "controversial" because of the untested status of these changes on multiple platforms, but otherwise I like the principle, as I commented in your Pull Request a while back.
CC @rkwright @clebeaupin @llemeurfr