Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed some memory leak issues. #279

Closed
wants to merge 1 commit into from
Closed

Fixed some memory leak issues. #279

wants to merge 1 commit into from

Conversation

TrondKjeldas
Copy link

There were several cases where the mxml_load_data() function, when it bailed out with an error, did not release the 'node' variable before returning.

Also fixed memory leak in the testmxml.c file, which cause some annoyance when building the library for fuzzing.

@michaelrsweet michaelrsweet self-assigned this Feb 5, 2021
@michaelrsweet michaelrsweet added the investigating Investigating the issue label Feb 5, 2021
@michaelrsweet
Copy link
Owner

@TrondKjeldas Thanks for this, I'll review when I get a chance but at first glance looks reasonable.

@michaelrsweet michaelrsweet added bug Something isn't working priority-medium and removed investigating Investigating the issue labels Oct 26, 2021
@michaelrsweet michaelrsweet added this to the Stable milestone Oct 26, 2021
@michaelrsweet michaelrsweet linked an issue Oct 26, 2021 that may be closed by this pull request
@michaelrsweet
Copy link
Owner

[master bd4eb86] Fix potential memory leak in mxmlLoadXxx (Issue #278, Issue #279)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working priority-medium
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Memory leak in mxml_load_data() error handling
2 participants