search

coder / code-server

VS Code in the browser
https://coder.com
MIT License
66.51k stars 5.45k forks source link

Git | Source control extension always stuck on running or processing for too long blocking other tools #6747

Closed jomoflash closed 2 months ago

jomoflash commented 3 months ago

Is there an existing issue for this?

OS/Web Information

Steps to Reproduce

  1. This happens intermittently
  2. After a long period working on a project

Expected

Git or inbuilt Source control extension should run immediately, and not block other activities like file creation and other extensions.

Actual

There is no visibility into what the source control extension is actually running for too long, or I have a knowledge gap on identifying the cause from the logs. Issue occurs even on small git based projects with little activities. requiring me to restart code-server every time which still doesn't help. Git gutter or Source Control gutter also stops working when issue occurs.

Logs

No response

Screenshot/Video

image

Does this bug reproduce in native VS Code?

No, this works as expected in native VS Code

Does this bug reproduce in GitHub Codespaces?

I did not test GitHub Codespaces

Are you accessing code-server over a secure context?

Notes

No response

code-asher commented 3 months ago

If you are able to test on Codespaces that would help us figure out whether this is an upstream issue with VS Code itself or an issue with code-server.

Does it happen without any extensions installed?

Does anything here help? https://stackoverflow.com/questions/65658602/file-operations-taking-long-time-receiving-running-file-save-delete-create

There is also a files.participants.timeout setting that you could experiment with.

I am not sure if there is a good way to debug file participants, but the VS Code folks upstream might have some ideas.

jomoflash commented 2 months ago

Thanks @code-asher, I have disabled all extensions globally except for few ones I'm using in the current workspace. I will post update here in about 24hrs on it's status. Thanks for the help

jomoflash commented 2 months ago

I'll go ahead and close this issue, issue is resolved after disabling all other extensions.

I would also appreciate if anyone can help with tips on identifying the culprit, possibly log watching or profiling extensions.

code-asher commented 2 months ago

You might have to use trial-and-error, test one extension at a time.

But if you run with --log verbose you will get a lot more output, so maybe something there will be useful. You can see it on stdout or in ~/.local/share/code-server/logs or in the Output panel inside VS Code (there is a dropdown for different logs in the Output panel, check them all).

One suggestion is when this happens, type Show Running Extensions into the command palette, and see if any of the extensions say they are inactive (https://stackoverflow.com/questions/60271767/running-save-participants-runs-forever-on-file-save).

Also, at the bottom you see where it says Creating na.js? I wonder if you hover over or click that whether it tells you anything else?