Vscode: blank screen occured when opening folder in WSL

Created on 10 Oct 2019  路  5Comments  路  Source: microsoft/vscode

Everything is ok before today. Then vscode go to blank if I try to open any folder in wsl after update. (it still works well in windows)

  • VSCode Version: 1.39.0 (auto update today)
  • OS Version: Windows 10 Version 1903

I have tryied to disable all extensions in wsl and windows manually (except remote-wsl extension), but it's still not working.

Can anyone tell me how to find out what's wrong?

ok
crash

picture mayeths

Most helpful comment

The log file I posted previously would indicate the persisted workspace state is corrupt or no longer compatible. I have left both markdown extension uninstalled. To get past this, here are the steps I followed to get my project loaded in vs code.

In WSL environment:

  • inspect meta.json located in each subdirectory of ~/.vscode-server/data/User/workspaceStorage
  • note the subdirectory name (for example 'aa4fce3b371fd7b658b113df4e3fb3d2') which contains the meta.json relating to the project that is causing problems

In Windows:

  • locate and delete or rename the workspace storage folder corresponding to the subdirectory name you identified previously. for me, that was located in the folder 'C:\Users\\AppData\Roaming\Code\User\workspaceStorage.
  • now try to load your problem project - should load fine now.
picture CaseyChester on 10 Oct 2019
👍5

All 5 comments

i am experiencing the same except only on one specific project. I first experienced this same behavior after installing yzhang.markdown-all-in-one and bierner.markdown-preview-github-styles extensions while editing a README.md file in this one node project. I have since uninstalled both extensions, but the problem persists. I have another node project via WSL that loads fine.

CaseyChester picture CaseyChester on 10 Oct 2019
👍1

yeah I also have markdown-all-in-one @CaseyChester ! You mention me the markdown's preview lost its style after update(I was too busy to treat it as a bug before). And exactly I have only one project in wsl so thought it's a normal bug in wsl :(

mayeths picture mayeths on 10 Oct 2019

I believe the error causing the problem is captured in the following log file.

renderer1.log

CaseyChester picture CaseyChester on 10 Oct 2019

The log file I posted previously would indicate the persisted workspace state is corrupt or no longer compatible. I have left both markdown extension uninstalled. To get past this, here are the steps I followed to get my project loaded in vs code.

In WSL environment:

  • inspect meta.json located in each subdirectory of ~/.vscode-server/data/User/workspaceStorage
  • note the subdirectory name (for example 'aa4fce3b371fd7b658b113df4e3fb3d2') which contains the meta.json relating to the project that is causing problems

In Windows:

  • locate and delete or rename the workspace storage folder corresponding to the subdirectory name you identified previously. for me, that was located in the folder 'C:\Users\\AppData\Roaming\Code\User\workspaceStorage.
  • now try to load your problem project - should load fine now.
CaseyChester picture CaseyChester on 10 Oct 2019
👍5

wow that also works for me!(remove related dir in windows) Thanks for @CaseyChester 's solution, I should close this now.

mayeths picture mayeths on 11 Oct 2019
Was this page helpful?
0 / 5 - 0 ratings

Related issues

lukehoban picture lukehoban  路  3Comments
omidgolparvar picture omidgolparvar  路  3Comments
trstringer picture trstringer  路  3Comments
NikosEfthias picture NikosEfthias  路  3Comments
borekb picture borekb  路  3Comments