It's a rendering issue, seems like, which is interesting because the mouse cursor does change and I can close a Chrome window if I click on the x on the only opened tab. But eventually, after a long while everything will start working again. Opening a new tab in Chrome via the Windows taskbar will show a white window. Oddly enough a Chrome window not on default profile (the one I had open for debugging) responds just fine. Just connecting over RDP will hang VS Code and my primary Chrome window. I have 3 Chromium-based windows opened: VSCode, Chrome with default profile and Chrome with a non-default profile (debugging window). It happens on first connect and also when I lose internet (spotty WiFi) and reconnect. I'm working remotely for vacation and haven't been local. Not specific to VS Code and not specific to Local/Remote changing. If you Keep Waiting, it will never come back. If you choose "Reopen", a new instance of VSCode will launch and will work fine. You can reopen or close the window or keep waiting" After about 15 seconds, you'll get a popup that says: ![]() 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |