v: fix all memleaks to enable memleak detection #23200
Merged
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
spytheman
reviewed
Dec 18, 2024
spytheman
reviewed
Dec 18, 2024
spytheman
approved these changes
Dec 18, 2024
|
I think we may have to skip the orm tests again for now (the ones that use sqlite) 🤔 . |
Ok, I'll treat the known cases in the .suppressions file. |
|
Some sqlite tests were fixed because indirect leak was spotted on gcc sanitizer. |
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 PR aims to fix all memleak found on sanitize tests for enabling detect_leaks=1
PS: Some sqlite test were fixed because indirect leak was spotted on gcc sanitizer.
Huly®: V_0.6-21637