DevTools fails to reconnect.
Reported by
adr...@onezerohosting.com,
Jun 19 2017
|
||||||
Issue description
Chrome Version : Version 60.0.3112.24 (Official Build) (64-bit)
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
Safari:
Firefox:
IE:
What steps will reproduce the problem?
(1) Open a dedicated devtools inspector url using any node.js debugger process to connect to such as http://localhost:9222/devtools/inspector.html?ws=127.0.0.1:9229/95701083-42e5-4c3d-984c-5065e56210e5 (this should still be supported when not using the about://inspect feature).
(2) Continuously reload the page.
What is the expected result?
DevTools should connect.
What happens instead?
In a short time DevTools will fail to reconnect to the node.js debugger (websocket, in this case 9229) connection, and you'll be presented with the "Debugging connection was closed. Reason: Websocket disconnected Reconnect when ready by reopening DevTools.'
Please provide any additional information below. Attach a screenshot if
possible.
,
Jun 20 2017
The URL was only an example. You need to debug a node.js program on your end using the inspect flag upon which time you will be able to connect to a similar url (but with a different websocket uuid ending instead of '95701083-42e5-4c3d-984c-5065e56210e5')
,
Jun 20 2017
Thank you for providing more feedback. Adding requester "krajshree@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 21 2017
This issue seems to be out of TE-scope. Hence adding label TE-NeedsTriageHelp for further investigation. Thanks...!!
,
Jun 21 2017
Does this mean the problem was confirmed/duplicated on your end?
,
Jun 28 2017
Hey Adrian, we're gonna need more details. Here's my guess at the flow: 1. `node --inspect app.js` 2. you open up dedicated debugger 3. you debug things and then ctrl-c node 4. restart `node --inspect app.js` and the dedicated window auto-reconnects. you debug. * you repeat this a few times (like 5-ish?) 5. you restart `node --inspect app.js` but this time the dedicated window stays disconnected. it shows the message in your screenshot. Is this how it happens? Also in this case can you open up http://localhost:9229/json/version and http://localhost:9229/json/list and paste their contents?
,
Aug 8 2017
I think the bug (if there is one) might be on the node's websocket side.
,
Oct 19 2017
No way to reproduce this, have not seen other reports.
,
Mar 23 2018
Hello, friends.
I have the same mistake. It seems that the error occurs when the module is compiled.
If the module is not opened on the "Sources" tab, then the error does not occur.
If the module is opened, there is an error in the console:
"Connection is closed, can not dispatch pending Runtime.compileScript
compileScript @ inspector.js: 4980 "
In line # 4980 of the module "Inspector.js" the following code is executed:
"var response = await this._agent.invoke_compileScript ({expression: expression, sourceURL: sourceURL, persistScript: persistScript, executionContextId: executionContextId})"
where "expression" is the code of my module.
What is interesting is that a month ago there was no mistake on the same project. Probably, something has changed in the environment.
Google Chrome version 65.0.3325.181, (64 bit)
Windows version 10
node.js version 8.10.0 (64 bit)
Projects on which I test:
https://github.com/oknosoft/windowbuilder-parametric
https://github.com/oknosoft/windowbuilder-planning
script: node --inspect ./index
A colleague who sits next to you does not reproduce the error.
I will be grateful for any help.
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by krajshree@chromium.org
, Jun 20 2017Labels: Needs-Feedback
45.4 KB
45.4 KB View Download