High CPU usage

[FREEZX]

Sometimes SourceGit jumps to 50-80% of CPU usage and pretty much locks up. I noticed that after force-closing it in this state and running git status after this state, git is running an index refresh for a few minutes. After that's done, SourceGit is back to working normally. Otherwise, if I just start it again normally without doing git status in terminal, it goes back to high CPU usage + locked up.

My guess is that SourceGit likely spams git commands without waiting on at least one of the commands to finish normally, so there are likely multiple commands triggering index refresh.

[love-linger]

I attach great importance to issues such as program startup speed and operating performance, yet many users pay no attention to these aspects. They always expect more information to be displayed, which may require running more git commands to obtain.

For git status command, to avoid requiring optional locks, SourceGit already enabled the --no-optional-locks option.

[FREEZX]

Interesting, could be some of the other git commands are getting blocked because the index is not refreshed. I'm generally happy with the performance, but this is a hard lock. Let ne know if there's anything I can do to share more info next time it happens

[love-linger]

And the High CPU usage issue may be caused by animations in AvaloniaUI, such as the loading icon animation and the indeterminated progress bar while waiting the git process to complete.

[love-linger]

One more thing, when an action is triggered by user, such as Fetch/Pull/Push .etc, SourceGit usually stops the file-system watcher (which is used to detect which part of information is outdated), and just waits that git command to complete. After the git command finished, SourceGit will re-enable the file-system watcher.

It means that this issue may caused by updating informations, such as remotes/branches/tags/commits/submodules/worktrees. There may be multiple git commands that run in parallel.