Open
Conversation
Author
Issue: The function did not free partition column names, auxiliary column names, metadata column names, and metadata chunk shadow table names. Fix: Added three loops to free this memory:
Issue: In the error path, only vec0_free(pNew) was called to free member variables, but the pNew structure itself was not freed. Fix: Added sqlite3_free(pNew) after vec0_free(pNew).
Issue: zSql allocated via sqlite3_mprintf was never freed. Fix: Added sqlite3_free((void *)zSql) immediately after the sqlite3_prepare_v2 call.
Issue: zSql was not freed in two places:
Fix: Added sqlite3_free((void *)zSql) after each sqlite3_prepare_v2 call.
Issue:
Fix:
|
mceachen
added a commit
to photostructure/sqlite-vec
that referenced
this pull request
Feb 10, 2026
- vec_eachFilter: free pzErrMsg on error to prevent leak - vec_slice: use goto done instead of return in INT8 and BIT cases to ensure vector cleanup is called on malloc failure These were the last 3 unfixed memory leaks from upstream PR asg017#258. The other 4 issues from that PR were already addressed in previous commits. Upstream-PR: asg017#258
mceachen
added a commit
to photostructure/sqlite-vec
that referenced
this pull request
Feb 10, 2026
Add test-error-paths.py with 30 tests specifically targeting error-handling code paths that previously had memory leaks (fixed in PR asg017#258). These tests ensure that error paths are exercised by the test suite so that memory leaks would be caught by sanitizers (ASan/LSan) if reintroduced. Tests cover: - vec_each with invalid inputs (NULL, wrong types, malformed JSON, empty arrays) - vec_slice error conditions (NULL, invalid types, bad indices) - vector_from_value error paths (mismatched types/dimensions in distance/add/sub) - vec0 INSERT/KNN errors (NULL, dimension mismatches, type mismatches) - Metadata operations with invalid inputs - Repeated error operations to stress-test cleanup paths Note: malloc failure paths (OOM conditions) are not tested as they require fault injection (SQLITE_TESTCTRL_FAULT_INSTALL) which is not available in the standard build. The fixes ensure proper cleanup via 'goto done' instead of early 'return' statements. Related: Upstream PR asg017#258
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
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.
I found a few memory leaks in the code and attempted to fix them. Could you please take a look and confirm whether the fixes are correct? I’m not entirely sure, but the changes are as follows: