Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error running browser: Cannot call write after a stream was destroyed

See original GitHub issue

Run with debug (Chrome preview) results in the following error:

Error running browser: Cannot call write after a stream was destroyed

I have installed the companion (or it was done for me) outside the remote container and in the remote container I have installed the workspace plugin vscode-js-nightly.

Version: 1.45.1
Commit: 5763d909d5f12fe19f215cbfdd29a91c0fa9208a
Date: 2020-05-14T08:27:22.494Z
Electron: 7.2.4
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Linux x64 5.4.0-31-generic

Issue Analytics

State:
Created 3 years ago
Comments:6 (2 by maintainers)

Top GitHub Comments

1reaction

connor4312commented, May 29, 2020

I’m having trouble reproducing this. Can you please do the following:

Verify that you have the extension id:ms-vscode.js-debug-companion installed on your local machine
Enable trace: true in your launch config, and share the logs if you’re able

0reactions

80saxcommented, Jul 25, 2020

I think the error is present using “request”: “launch” https://github.com/microsoft/vscode-js-debug/issues/659