fix memory leaks #294
Open
fix memory leaks #294
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
TaeZStkyoht
force-pushed
the
fix-memory-leak
branch
3 times, most recently
from
add86ae to
d8fa737
Compare
- BIGNUM must be freed both on tpm2tss_tpm2data_write and tpm2tss_tpm2data_read: definitely lost: 24 bytes in 1 blocks indirectly lost: 8 bytes in 1 blocks - TSSPRIVKEY's parent, privkey and pubkey members don't need to be allocated explicitly, because TSSPRIVKEY_new already does: definitely lost: 72 bytes in 3 blocks indirectly lost: 0 bytes in 0 blocks - TPM2_DATA* returned from RSA_get_app_data can be returned directly genkey_rsa() because RSA_free() doesn't free this item: definitely lost: 2,248 bytes in 1 blocks indirectly lost: 0 bytes in 0 blocks - update .gitignore to cover more generated files Signed-off-by: Oguzhan Turk <[email protected]>
TaeZStkyoht
force-pushed
the
fix-memory-leak
branch
from
d8fa737 to
1f35b76
Compare
kalvdans
approved these changes
Apr 4, 2025
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.
definitely lost: 24 bytes in 1 blocks
indirectly lost: 8 bytes in 1 blocks
definitely lost: 72 bytes in 3 blocks
indirectly lost: 0 bytes in 0 blocks
definitely lost: 2,248 bytes in 1 blocks
indirectly lost: 0 bytes in 0 blocks