You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Does this issue occur when all extensions are disabled?: Yes
When I try to launch Chromium using the "Run and Debug" option in VSCode, it fails after a couple seconds with an error saying "Unable to attach to browser".
I've tried opening the launch.json and adding the runtimeExecutable path to my Chromium install, and it still gives the same error.
I've tried uninstalling Chromium and reinstalling using sudo apt install chromium-browser, same error.
Chrome Version: 111.0.5563.146
My launch.json:
{
// Use IntelliSense to learn about possible attributes.
// Hover to view descriptions of existing attributes.
// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
"version": "0.2.0",
"configurations": [
{
"type": "chrome",
"request": "launch",
// "runtimeExecutable": "/snap/bin/chromium",
// "runtimeExecutable": "/usr/bin/chromium-browser",
"name": "Launch Chrome against localhost",
"url": "http://localhost:4000",
"webRoot": "${workspaceFolder}"
}
]
}
VS Code version: Code 1.77.0 (7f329fe, 2023-03-29T10:05:35.165Z)
OS version: Linux x64 5.15.0-1032-oracle snap
Modes:
Sandboxed: No
I've dug into the developer logs, and I see this when I try to launch:
==> sharedprocess.log <==
2023-03-31 20:06:40.144 [error] [uncaught exception in sharedProcess]: Cannot read properties of undefined (reading 'then'): TypeError: Cannot read properties of undefined (reading 'then')
at h.s (/snap/code/123/usr/share/code/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:23:5588)
at h.q (/snap/code/123/usr/share/code/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:23:4988)
at /snap/code/123/usr/share/code/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:23:4377
at E.invoke (/snap/code/123/usr/share/code/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:19:145)
at u.deliver (/snap/code/123/usr/share/code/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:19:2121)
at l.fire (/snap/code/123/usr/share/code/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:19:1729)
at MessagePortMain.B (/snap/code/123/usr/share/code/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:17:23772)
at MessagePortMain.emit (node:events:526:28)
at MessagePortMain._internalPort.emit (node:electron/js2c/utility_init:5:364)
I was still having problems in v1.77.3, turns out I had VSCode installed through snap. I tried installing with the .deb package and that seems to have fixed the issue: https://code.visualstudio.com/docs/setup/linux
Type: Bug
Does this issue occur when all extensions are disabled?: Yes
When I try to launch Chromium using the "Run and Debug" option in VSCode, it fails after a couple seconds with an error saying "Unable to attach to browser".
I've tried opening the
launch.json
and adding theruntimeExecutable
path to my Chromium install, and it still gives the same error.I've tried uninstalling Chromium and reinstalling using
sudo apt install chromium-browser
, same error.Chrome Version: 111.0.5563.146
My launch.json:
VS Code version: Code 1.77.0 (7f329fe, 2023-03-29T10:05:35.165Z)
OS version: Linux x64 5.15.0-1032-oracle snap
Modes:
Sandboxed: No
System Info
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: disabled_software
multiple_raster_threads: enabled_on
opengl: disabled_off
rasterization: disabled_software
raw_draw: disabled_off_ok
skia_renderer: enabled_on
video_decode: disabled_software
video_encode: disabled_software
vulkan: disabled_off
webgl: unavailable_software
webgl2: unavailable_software
webgpu: disabled_off
Extensions (24)
A/B Experiments
The text was updated successfully, but these errors were encountered: