fix: memory leak in Python bytes object retrieval #18
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
P403n1x87
force-pushed
the
fix/pybytes-memleak
branch
2 times, most recently
from
9ec8daf to
1be260f
Compare
P403n1x87
force-pushed
the
fix/pybytes-memleak
branch
from
1be260f to
566ddb8
Compare
Fixed a memory leak when retrieving byte arrays (line number tables) that were never deallocated after use. We move to automatic memory management with smart pointers to allow for the clean up to happen.
P403n1x87
force-pushed
the
fix/pybytes-memleak
branch
from
566ddb8 to
38bd58a
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.
Fixed a memory leak when retrieving byte arrays (line number tables) that were never deallocated after use. We move to automatic memory management with smart pointers to allow for the clean up to happen.