Skip to content
This repository has been archived by the owner on Oct 12, 2022. It is now read-only.

cannot connect to runtime process (timeout after 3000ms) #17

Closed
weinand opened this issue Dec 2, 2015 · 1 comment
Closed

cannot connect to runtime process (timeout after 3000ms) #17

weinand opened this issue Dec 2, 2015 · 1 comment
Assignees
Labels
Milestone

Comments

@weinand
Copy link
Contributor

weinand commented Dec 2, 2015

From @sangrambal on December 2, 2015 0:42

When creating Helloworld extension , got the following error message after F5
cannot connect to runtime process (timeout after 3000ms)

Copied from original issue: microsoft/vscode#893

@weinand
Copy link
Contributor Author

weinand commented Dec 2, 2015

I suspect that a timeout of 3000ms is just not enough to launch and attach to the extension host process.

However in VS Code 0.10.x I did not make the timeout longer because the same timeout is used when VS Code polls for a terminated extension host process. So making it longer would mean that you cannot start a new debug session, because VS Code is still waiting for the old session to timeout.

For the next release we plan to eliminate the polling which makes it possible to increase the attach timeout to whatever we need. The associated issue is this: microsoft/vscode#855

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants