Fix memory leak reported by clang tool #149
Open
Conversation
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
sarroutbi
changed the title
sarroutbi
force-pushed
the
202405161612-fix-possible-memleak
branch
2 times, most recently
from
d531e4b to
c3a5205
Compare
sarroutbi
changed the title
This memory leak, although not easily reproducible, has been detected by Static Application Security Testing tool (trhough clang compiler). This fix eliminates it. Signed-off-by: Sergio Arroutbi <[email protected]>
sarroutbi
force-pushed
the
202405161612-fix-possible-memleak
branch
from
c3a5205 to
848e64e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This memory leak, although not easily reproducible, has been detected by Static Application Security Testing tool. This fix eliminates it.