search

microsoft / vscode

Visual Studio Code
https://code.visualstudio.com
MIT License
163.58k stars 29.02k forks source link

VSCode hangs when switching between local login and remote desktop login #167556

Open shaunco opened 1 year ago

shaunco commented 1 year ago

Does this issue occur when all extensions are disabled?: Yes

Steps to Reproduce:

  1. Log in locally to your Windows desktop
  2. Set scaling to 150% (Control Panel-->System-->Display)
  3. Take note of the display resolution
  4. From a local login, open a project in VSCode
  5. Lock the local workstation (do not log out)
  6. From a different system where scaling is set to something other than 150%, and preferably the resolution is also different
  7. Open Remote Desktop Connection
  8. Enter the IP of the original system
  9. Click Connect
  10. Log in

VSCode will resize the outermost frame of the window, but will leave Explorer and code windows smaller, and will be unresponsive to mouse or keyboard input. After about 15 seconds, you'll get a popup that says:

"The window is not responding. You can reopen or close the window or keep waiting"

If you choose "Reopen", a new instance of VSCode will launch and will work fine. If you Keep Waiting, it will never come back.

soulee-dev commented 6 months ago

Struggle same issue now. This should be fixed.

wbjlix commented 4 months ago

I too had the same problem. It was determined that there was a problem with IME-related settings. It was resolved immediately by using the option to use the previous version's IME. Very happy.

image

image

ValueXu commented 4 months ago

I found an extremely ugly but effective temporary solution to recover from an unresponsive window input without needing to restart VSCode.

When the window becomes unresponsive, losing and regaining focus can restore operation, but if you enter any character again, the window will freeze.

In a fortuitous circumstance, I found that you can continuously input any characters(Press a character button without releasing it) when the window freezes, then click any other character-inputable area within the frozen window (while still inputting characters), then make the window to lose focus and regain it. This will restore the window from freezing.

You might not have enough hands to make the window lose focus, but remember, the Windows key (Win key) can also do the trick.

Thanks！It works for me. And sadly, the bug still exists after a year.(T_T)

baizebing commented 4 months ago

This should fix (at least partially) once VSCode upgrade to a electron version that based on Chromium 124.0.6367.0 https://chromium-review.googlesource.com/c/chromium/src/+/5365680

When will vscode update to latest chromium? Is there any plan? The issue has been anoying me for years!

reitowo commented 4 months ago

When will vscode update to latest chromium? Is there any plan? The issue has been anoying me for years!

Sadly it has been reverted by Microsoft. They say they will internally see this bug, but didn't give any updates currently.

Everyone concern about this should give some pressure at:

https://issues.chromium.org/issues/328859185

WilliamKyle commented 4 months ago

https://github.com/microsoft/vscode/issues/214394 Waiting for new electron

jackyzy823 commented 4 months ago

According to the comment 37 , this is a Windows TSF framework bug which is confirmed and fixed by Microsoft and the fix should be released to public July - August.

liuyxpp commented 4 months ago

According to the comment 37 , this is a Windows TSF framework bug which is confirmed and fixed by Microsoft and the fix should be released to public July - August.

Ah, finally!

cnrat commented 1 month ago

According to the comment 37 , this is a Windows TSF framework bug which is confirmed and fixed by Microsoft and the fix should be released to public July - August.

It’s August 22nd, 2024, and this issue is still bothering me—classic Microsoft.

ValueXu commented 1 month ago

According to the comment 37 , this is a Windows TSF framework bug which is confirmed and fixed by Microsoft and the fix should be released to public July - August.

No any futher progress for this issue until now, sad and mad.

xty435768 commented 1 month ago

still waiting for update...

jackyzy823 commented 1 month ago

Update from https://issues.chromium.org/issues/328859185#comment45 :

just got a response from Windows team. Unfortunately, the original fix was scheduled to release in September. However, there was a regression, so the fix was reverted. The new fix is under test and won't be released until several months.

ValueXu commented 1 month ago

Update from https://issues.chromium.org/issues/328859185#comment45 :

just got a response from Windows team. Unfortunately, the original fix was scheduled to release in September. However, there was a regression, so the fix was reverted. The new fix is under test and won't be released until several months.

No! I'm gonna use Linux.