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
{{ message }}
Repository navigation
Index refresh is (sometimes) extremely slow, locks up the app whilst refreshing #181
I'm seeing "Refreshing index" and the activity indicator for around 5 seconds, during which time the UI is totally unresponsive. If I then press ⌘R to perform another refresh, it completes in a fraction of a second.
Does anyone have any clues why this is happening?
Reacted by Ben Fritsch, Igor Ryzhov, David Brooks, Dorian Kind, Ian VanSchooten, Nick Brachet, Francis Gulotta and tewe
changed the title [-]Index refresh is extremely slow, locks up the app whilst refreshing[/-][+]Index refresh is (sometimes) extremely slow, locks up the app whilst refreshing[/+]on Feb 21, 2019
This continues to happen even in small repositories. I'm also realizing they have large .gitignored directories (eg node_modules) and that might be part of it.
Definitely a UX issue, for now it seems @IanVS suggestion of turning off Watch for changes in repository does actually improve the situation quite a bit.
Activity
[-]Index refresh is extremely slow, locks up the app whilst refreshing[/-][+]Index refresh is (sometimes) extremely slow, locks up the app whilst refreshing[/+]dbrnz commentedon Apr 20, 2019
This has only just started happening for me and I'm wondering if a recent Mojave update might be the culprit...
dbrnz commentedon Apr 20, 2019
Hmm, all my doing -- I had a newly created output directory, which wasn't in
.gitignore, that had almost 50,000 files in a sub-directory tree...IanVS commentedon Dec 30, 2019
I have experienced this as well, with a recently built app on Catalina. For now I've turned off
Watch for changes in repository.reconbot commentedon Jun 11, 2021
This continues to happen even in small repositories. I'm also realizing they have large .gitignored directories (eg node_modules) and that might be part of it.
lericson commentedon Sep 23, 2025
Definitely a UX issue, for now it seems @IanVS suggestion of turning off Watch for changes in repository does actually improve the situation quite a bit.