Background task from Git panel and Debugging panel blocked in loading position #236485
Comments
|
Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.96.0. Please try upgrading to the latest version and checking whether this issue remains. Happy Coding! |
|
Before I use the new version but I also have the problem, I try to rollback
to identify if the problem is coming from the upgrade version but not,
problem is still here.
|
|
Also started seeing this problem yesterday. |
|
So you do see it in 1.96? What language are you debugging? Can you share a screenshot? Not totally clear what you see.. |
|
I'm working on my vscode project with or without the debugger turned on.
After several code modifications, the source control becomes pending, and
then it is impossible to restart the debugger, to have copilot inline or in
chat, and the source control never recovers as it should without restarting
VSCode completely.
Sometimes source control and debugger are in pending status, it depends.
But each time I need to reboot VSCode.
I tried to uninstall / reinstall VSCode, remove cache from VsCode, but the
problem persists.
|
|
Can you try disabling extensions (eg F1 > "Reload With Extensions Disabled") and see if it still happens? It sounds lik this happens even when just editing files, not using the debugger, right? I'm guessing that some extension has the extension host process stuck. Do you see a process stuck with high CPU when this happens? You can check Help > Open Process Explorer to see |
|
I think I am experiencing something similar. It "started to happen" some time this week, I believe. I was on an earlier version of code 1.8*, and in an effort to circumvent this, upgraded to 1.96, where this is still happening. I am super confused and have never seen something like this before. Let me go into some more detail: When this "happens", my VSCode all of a sudden partially freezes up. What I mean by this is:
Reloading the window via I am using code on my local machine (Ubuntu 22.04) to connect to a remote server via SSH. On the remote server I have a docker container running, to which I connect again, and where I work in. I work in a mostly Python (and some C++ files environment). I use the following extensions: Since I rely on some of these extensions to be able to reach the environment where I can reproduce this issue, I can't really run without extensions. However, running without any extensions does seem to make this go away. I tested this connecting to a different server, and connecting also from a different machine (Ubuntu 20.04), just to ensure that it's not something wrong with either machine. This is my VSCode, but this definitely also happened on an earlier version.
Does seem to make this go away.
Yes, seems to be the case.
Nothing out of the ordinary |
|
I think there might be a number of related issues |
|
Looks like this should be fixed via microsoft/vscode-python#24633 |
roblourens
added
the
*duplicate
Type: Bug
After launching the debugger or modifying the code, the source control and the Run and Debug sections switch to a loading version (with the clock icon), and it becomes impossible to restart the debugger or have extensions like Copilot working. You have to restart VSCode for it to work again.
VS Code version: Code 1.95.3 (f1a4fb1, 2024-11-13T14:50:04.152Z)
OS version: Linux x64 6.8.0-49-generic
Modes:
System Info
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: enabled
video_encode: disabled_software
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: disabled_off
webnn: disabled_off
Extensions (6)
A/B Experiments
The text was updated successfully, but these errors were encountered: