Fix painfully slow refresh in repos with uncommitted large binary files#959
Merged
Murmele merged 2 commits intoMay 15, 2026
Merged
Conversation
Murmele
requested changes
May 14, 2026
Owner
Murmele
left a comment
There was a problem hiding this comment.
Thank you for the investigation into this problem!
Murmele
approved these changes
May 14, 2026
This was referenced May 14, 2026
429d56d to
cf9b03a
Compare
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.
This is a partial port of gitahead/gitahead#601
I've tested with a 2.5GiB file uncommitted in the repo, and the refresh is pretty decent. Without the fix, Gittyup would just sit there and chew RAM and CPU like crazy. I'm sure it would result in an OOM crash eventually, but I didn't wait for that. This is quite simply night and day difference.
This partially addresses #652 and #765, and might help #523