Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot connect to runtime process, timeout after 10000 ms #68

Closed
cosminalco opened this issue Mar 3, 2019 · 10 comments · Fixed by #97
Closed

Cannot connect to runtime process, timeout after 10000 ms #68

cosminalco opened this issue Mar 3, 2019 · 10 comments · Fixed by #97
Labels
bug Something isn't working

Comments

@cosminalco
Copy link

Actually is working perfectly but only after the second time I launch the debugger, the first time I get this error:
screenshot 15

The newcomers may think the extension is not working.

Maybe is because of Debugger for Chrome extension I don't know, I would be happy just know if there is somewhere I can increase that delay.

My launch.json:

{
  "version": "0.2.0",
  "configurations": [
    {
      "type": "browser-preview",
      "request": "launch",
      "name": "Browser Preview: Launch",
      "url": "http://localhost:5000/",
      "webRoot": "${workspaceFolder}/public"
    }
  ]
}
@auchenberg auchenberg added the bug Something isn't working label Mar 4, 2019
@auchenberg
Copy link
Owner

@cosminalco Would you happen to have other Chrome instances running in your machine?

@cosminalco
Copy link
Author

No, but maybe is because I'm using the portable version of VSCode from on a partition, Windows is on C: VSCode is in D:/Apps/VSCode

@eltoncezar
Copy link

Same issue here. Everything worked great till last week. But today I started getting this error. Can't make it work even after a second run.
I can confirm that there are no other Chrome instances running at the same time. I can also confirm that launching with Debugger for Chrome and the same configuration works just fine.

{
  "version": "0.2.0",
  "configurations": [
  // This do work
  {
    "name": "ng serve",
    "type": "chrome",
    "request": "launch",
    "preLaunchTask": "npm: start",
    "url": "http://localhost:4200/#",
    "webRoot": "${workspaceFolder}"
  },
  // This doesn't
  {
    "name": "Browser Preview: Launch",
    "type": "browser-preview",
    "request": "launch",
    "preLaunchTask": "npm: start",
    "url": "http://localhost:4200",
    "webRoot": "${workspaceFolder}"
  }]
}

@pavel-kalmykov
Copy link

Same happens to me, but it gives me another error:
image
This is my launch.json file:

{
  "version": "0.2.0",
  "configurations": [
    {
      "type": "browser-preview",
      "request": "launch",
      "name": "Browser Preview: Launch",
      "url": "http://localhost:8100",
      "webRoot": "${workspaceFolder}"
    }
  ]
}

BTW I use this for debugging an Ionic4 App and I'm running High Sierra.

@yoyoys
Copy link

yoyoys commented Apr 23, 2019

I'm using OSX Mojave, same problem here with vuejs(cli3)

@eltoncezar
Copy link

@auchenberg when this fix will be available at the marketplace OR how can I test it today? can you provide some info? I'm not familiar with building vs-code extensions. Thanks in advance.

@auchenberg
Copy link
Owner

@eltoncezar
Copy link

many many many thanks! it's working again!

@auchenberg
Copy link
Owner

Yay, glad to hear @eltoncezar

@kevinbarabash
Copy link

kevinbarabash commented Jan 2, 2020

I'm seeing this in 0.5.9. I can work around it it by opening Browser Preview manually and then running the launch command. This results in browser panels so I close the one I opened manually. Here's the launch config I'm using:

{
    "type": "browser-preview",
    "request": "launch",
    "name": "Browser Preview: Launch",
    "url": "http://localhost:9000",
    "webRoot": "${workspaceFolder}"
},

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants