[vscode-web] extension host process times out on startup

[thisisommore]

Bug description

The VsCode command to stop gitpod workspace is missing sometimes

Also this button doesn't work when the issue occurs

Steps to reproduce

Run any workspace and try to stop it after a while.
This most of the time works, but still more frequently I started seeing such issue

Workspace affected

No response

Expected behavior

The gitpod button should always be clickable and the stop workspace command always be available

Example repository

No response

Anything else?

After reloading the tab it works

[akosyakov]

Do you use stable or insiders? Is anything else working, i.e. do you have terminals, git integration and so on? It sounds like the extension host process does not start at all?

[thisisommore]

@akosyakov Yeah, I am using stable and Saas (not self-hosted), also the terminal works but the git integration doesn't.

[thisisommore]

Yeah, I guess some issue with the extension host process, I will try to reproduce it again and capture logs In dev tools, will it be helpful?

[mustard-mh]

Does refresh this page help? @thisisommore

[akosyakov]

@thisisommore You connection is good? VS Code tries to start up extensions for 1 minute and then gives up leaving such state usually.

You can also share your startup performance in such case, maybe there is something interesting:

Does refresh this page help? @thisisommore

👍 It should work like a workaround.

[thisisommore]

Does refresh this page help? @thisisommore

@mustard-mh Yes it does

[thisisommore]

@thisisommore You connection is good? VS Code tries to start up extensions for 1 minute and then gives up leaving such state usually.

You can also share your startup performance in such case, maybe there is something interesting:

Does refresh this page help? @thisisommore

👍 It should work like a workaround.

Got it will check

[shaal]

I've seeing this for the last few months, most time everything is good, sometimes a workspace loads without the "Gitpod extras", and a refresh of the tab fixes it.
I didn't find a way to reproduce it, for me it happens randomly. I use regular VSCode (not insiders).

@akosyakov can you write what information should we collect when it happens next time?