Optimize RAM During Analyze#20
Merged
Merged
Conversation
erikburt
approved these changes
Jun 22, 2026
Comment on lines
+826
to
+827
| cleanup() | ||
| return nil, nil, nil, err |
There was a problem hiding this comment.
Whats the reason behind calling cleanup() here and not just returning it? Seems like it will/should get called regardless.
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
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.
Analyzeon large results frequently hitsOOMerrors. This PR attempts to write to disk more often and have more general memory optimizations.