You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To Reproduce
my project is super big, which has around 140000 commits,
when use / to search a keywork in first commit message.
it stuck for a while, then crashed.
Expected behavior
improve searching speed. then no crash.
Screenshots
If applicable, add screenshots to help explain your problem.
Version info:
0.41.0
2.35.3
Additional context
Add any other context about the problem here.
Note: please try updating to the latest version or manually building the latest master to see if the issue still occurs.
The text was updated successfully, but these errors were encountered:
This is a known problem. What happens here is that normally lazygit only loads the first 300 commits, that's why it's tolerably fast even in huge repositories; however, when you scroll all the way down to the last of those 300 commits (or press > to get there quickly), lazygit loads all commits, and this currently takes so much memory that it either gets unbearably slow, or even crashes.
And the same happens when you press / to search: this also triggers loading all commits, on the assumption that you may want to search them all.
There has been some work on improving the memory consumption, see #2533. I'm planning on picking up that work again relatively soon, but I can't promise anything.
Describe the bug
To Reproduce
my project is super big, which has around 140000 commits,
when use / to search a keywork in first commit message.
it stuck for a while, then crashed.
Expected behavior
improve searching speed. then no crash.
Screenshots
If applicable, add screenshots to help explain your problem.
Version info:
0.41.0
2.35.3
Additional context
Add any other context about the problem here.
Note: please try updating to the latest version or manually building the latest
master
to see if the issue still occurs.The text was updated successfully, but these errors were encountered: