WSL2 and Java causes git blame to hang

[kropptrevor]

I can use the extensions fine for a time, but I've been encountering a problem where my VSCode instance will consume a lot of CPU and functionality will be reduced. Exiting VSCode completely and then restarting fixes it temporarily.

I had two windows open

1. Git Blame + Java extensions
2. Git Blame extension only

The problem showed up on only on 1.

Extension list 1:

vscjava.vscode-java-debug
waderyan.gitblame
vscjava.vscode-gradle
redhat.java
vscjava.vscode-java-test

Extension list 2:

waderyan.gitblame

---

status-before.txt
status-after.txt

Note that I ran the git blame incremental command that is showing up in the status and it completed instantly from the command line.

---

This causes side-effects like the following:
Source control hanging

Java language server hanging

---

Operating system: Windows
WSL/WSL2: Yes
Remote SSH folder: No
Remote folder with sync program: No
vscode version: 1.90.1
output from `git rev-list --all --count`: 535

[Sertion]

Hey Trevor. Thanks for for the detailed bug report!

This type of issue is very difficult to track down the root cause for. I've somewhat recently investigated a similar issue (#172) and the closest I could get to a reason was that there is something in the vscode extension host doing something unexpected when the extension is using a lot of CPU and/or memory.

If anyone has any ideas how to get to the bottom with this any help would be appreciated!