Resolve memory leaks #98
Open
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
In production, we noticed a steady increase in memory usage until our nodes would crash due to out of memory. Using valgrind and the pastebin below via
valgrind --leak-check=full node --expose-gc beamcoder.js, we discovered what appears to be memory leaks in the decoder, encoder, and filters due to frames and packets not being freed. This PR adds the necessaryav_frame_freeandav_packet_freecalls to avoid this memory leak. Apologies if the code is not ideal. I don't work in C++ day to dayhttps://pastebin.com/Q2fCP4qa