Fix memory leak in allphone_search.c #138
Merged
Conversation
This file contains hidden or 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
Running allphone_backtrace multiple times clears previously allocated segments, but no one ever clears the most recently allocated ones, creating a memory leak which Valgrind attributes to the most recent time allphone_backtrace was run. allphone_search_free seems like the obvious place to do clean it up.
Contributor
|
Thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Running allphone_backtrace multiple times clears previously allocated segments, but no one ever clears the most recently allocated ones, creating a memory leak which Valgrind attributes to the most recent time allphone_backtrace was run. allphone_search_free seems like the obvious place to do clean it up.