Fix memory leakage #153
Merged
Fix memory leakage #153
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
vin-huang
requested review from
jichangjichang,
hcman2 and
imcarsonliao
as code owners
vin-huang
force-pushed
the
fix_memory_leakage
branch
from
36ba1db
to
56b4c00
Compare
vin-huang
force-pushed
the
fix_memory_leakage
branch
from
56b4c00
to
86cae9d
Compare
vin-huang
force-pushed
the
fix_memory_leakage
branch
from
86cae9d
to
a34c93a
Compare
alex391a
approved these changes
Oct 2, 2024
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.
Found memory leakages when running sample code
Ex, valgrind --leak-check=full ./clients/staging/example_prune_stripUse SMARTE_DESTROYER and SMARTE_DESTROYER_NON_PTR to free the located memory and objects in the sample code