vscode: 1.77 you can no longer have any extensions on a remote container as of 10295b5

Does this issue occur when all extensions are disabled?: Yes (Error is the same, and IO is impacted)

I am updating this report with information I figured out this weekend.

Issue:

Inability to use any extensions on a remote container.
Extremely slow IO issues, causing file saving on remote to often fail.

Affected Version(s):

Version: 1.77.0 (user setup) Commit: 7f329fe6c66b0f86ae1574c2911b681ad5a45d63 Date: 2023-03-29T10:02:16.981Z Electron: 19.1.11 Chromium: 102.0.5005.196 Node.js: 16.14.2 V8: 10.2.154.26-electron.0 OS: Windows_NT x64 10.0.22621 Sandboxed: No

First Affected Version:

Version: 1.77.0-insider (system setup) Commit: 10295b5bae81a83b7d940f9d64756c115af662c8 Date: 2023-03-28T20:38:02.832Z Electron: 19.1.11 Chromium: 102.0.5005.196 Node.js: 16.14.2 V8: 10.2.154.26-electron.0 OS: Windows_NT x64 10.0.22621 Sandboxed: Yes

Last working version:

Version: 1.77.0-insider (system setup) Commit: c83f54aefc2dd212c01a42c57c930aa8a13af3a6 Date: 2023-03-24T05:23:09.316Z Electron: 19.1.11 Chromium: 102.0.5005.196 Node.js: 16.14.2 V8: 10.2.154.26-electron.0 OS: Windows_NT x64 10.0.22621 Sandboxed: Yes

Symptoms:

External extensions cannot be loaded.
Error in Spdlog.
Git is non-functional (due to dead extensions).
Reading/writing a file while connected to a remote container takes several minutes.
Disabling extensions doesn’t fix the IO issues.
High CPU usage spikes in VS Code. (Sometimes)

Other Environment Specific Issues: The issue occurs on multiple machines with different remote containers running Alpine docker ruby:2.7-alpine3.13. I have not tested other container types.

More Details and Screenshots:

Note: This is happening on both of my machines with multiple different remote containers, both running Alpine docker ruby:2.7-alpine3.13 in docker containers, but errors only happen when upgrading to version 1.77.0. I downgraded to 1.76.2, or actually, the insider version I list above as working and the issue solves.

I first noticed this because I couldn’t see my git anymore.

I notice that creating files will take forever and sometimes fail entirely:

I disabled all extensions using the Extension Bisect, and the IO issues were the same. It’s across multiple computers as different containers as well. Of course, since no extensions were loaded, I don’t know if I could load extensions.

The window output log is the only thing that seems to stand out to me. It goes into a reconnect loop. This does not happen on 1.76.2. But this is because there was not logging on this in 1.76.2 https://github.com/microsoft/vscode/commit/06b97f6be7312c5efd04de17e006444138237dd9#diff-8263ddc3ea4e33f1aefbc20b4bb091aa39d95ed193cf0f616cae3372d4fa929bL193-L207)

Possible Causes:

Theory 1) Changed location of extension internationalization folders for remotes without migrating previous locations.

When looking at the diff between the last working version and the broken version this most suspicious commit is this:

https://github.com/microsoft/vscode/commit/5e7a8d96005fe07e0e1b4efae8d992c2fcd59a24#diff-4c262f7afdd805a114b3aa50ecddacf8920239c2bbd18751412123f952b58e45R849-R851

It throws an error if the directory doesn’t exist and doesn’t attempt to create it. This could be problematic when a container is already installed with an older version of VSCode with the old directory for extension internationalization. However, I don’t know that this is the case since the issue also was reproducible when I did a clean docker install before attaching VSCode.

Theory 2) SPDLog was not built with the correct version of node.

See: (https://github.com/microsoft/vscode/issues/174605)

This is supported by:

The SPDLOG build was moved to NPM from yarn which changed pinnings. https://github.com/microsoft/node-spdlog/commit/8cd5932422c2f934f860ff4d735e97f380fd7b83
The Azure pipeline for building the package was modified around the time of this error.(https://github.com/microsoft/node-spdlog/pull/26)
SPDLOG received a changes to it’s package name in 1.77.0 as the package was renamed to @vscode/spdlog. (https://github.com/microsoft/node-spdlog/pull/27) NOTE: This was merged with a failing build.
The error log seems to point to spdlog, but not sure if it IS spdlog or if spdlog is simply showing up because that is the last item in the stack track.

The above also don’t exactly line up with where the error first appears in terms of versions I installed. However, I am not sure how the build pipeline is set up and may have taken some time for the changes in spdlog to end up being rebuilt with the changed node versions or package locations.

It’s hard to say. Hopefully the commits I provided can help someone with more knowledge of the system track it down.

I have not tried a minimal reproduction yet but this is what I would do:

Proposed Reproduction Steps

Create an ruby:2.7-alpine3.13 docker container.
Install vscode 1.76.x
Attach container to VS code “Attach VS Code To Container”
Install extensions on remote
Upgrade VSCode on host machine
Reload vscode and attach it and see if it breaks

Log:

2023-03-30 17:33:23.402 [info] Electron sandbox mode is enabled!
2023-03-30 17:33:23.423 [warning] Via 'product.json#extensionEnabledApiProposals' extension 'ms-vscode.vscode-selfhost-test-provider' wants API proposal 'testContinuousRun' but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check 'vscode.d.ts') or was abandoned.
2023-03-30 17:33:23.423 [warning] Via 'product.json#extensionEnabledApiProposals' extension 'ms-toolsai.jupyter' wants API proposal 'notebookControllerKind' but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check 'vscode.d.ts') or was abandoned.
2023-03-30 17:33:23.772 [info] Invoking resolveAuthority(attached-container)...
2023-03-30 17:33:23.772 [info] [LocalProcess0][resolveAuthority(attached-container,1)][0ms] obtaining proxy...
2023-03-30 17:33:24.495 [info] [LocalProcess0][resolveAuthority(attached-container,1)][722ms] invoking...
2023-03-30 17:33:25.500 [info] [LocalProcess0][resolveAuthority(attached-container,1)][1727ms] waiting...
2023-03-30 17:33:26.500 [info] [LocalProcess0][resolveAuthority(attached-container,1)][2726ms] waiting...
2023-03-30 17:33:27.500 [info] [LocalProcess0][resolveAuthority(attached-container,1)][3727ms] waiting...
2023-03-30 17:33:28.496 [info] [LocalProcess0][resolveAuthority(attached-container,1)][4723ms] waiting...
2023-03-30 17:33:29.497 [info] [LocalProcess0][resolveAuthority(attached-container,1)][5724ms] waiting...
2023-03-30 17:33:30.501 [info] [LocalProcess0][resolveAuthority(attached-container,1)][6728ms] waiting...
2023-03-30 17:33:31.501 [info] [LocalProcess0][resolveAuthority(attached-container,1)][7728ms] waiting...
2023-03-30 17:33:32.496 [info] [LocalProcess0][resolveAuthority(attached-container,1)][8723ms] waiting...
2023-03-30 17:33:33.502 [info] [LocalProcess0][resolveAuthority(attached-container,1)][9729ms] waiting...
2023-03-30 17:33:34.502 [info] [LocalProcess0][resolveAuthority(attached-container,1)][10728ms] waiting...
2023-03-30 17:33:35.497 [info] [LocalProcess0][resolveAuthority(attached-container,1)][11724ms] waiting...
2023-03-30 17:33:36.508 [info] [LocalProcess0][resolveAuthority(attached-container,1)][12735ms] waiting...
2023-03-30 17:33:37.508 [info] [LocalProcess0][resolveAuthority(attached-container,1)][13735ms] waiting...
2023-03-30 17:33:38.503 [info] [LocalProcess0][resolveAuthority(attached-container,1)][14730ms] waiting...
2023-03-30 17:33:39.498 [info] [LocalProcess0][resolveAuthority(attached-container,1)][15724ms] waiting...
2023-03-30 17:33:40.496 [info] [LocalProcess0][resolveAuthority(attached-container,1)][16723ms] waiting...
2023-03-30 17:33:41.505 [info] [LocalProcess0][resolveAuthority(attached-container,1)][17732ms] waiting...
2023-03-30 17:33:42.508 [info] [LocalProcess0][resolveAuthority(attached-container,1)][18735ms] waiting...
2023-03-30 17:33:43.155 [info] [LocalProcess0][resolveAuthority(attached-container,1)][19382ms] returned 127.0.0.1:36669
2023-03-30 17:33:43.155 [info] resolveAuthority(attached-container) returned '127.0.0.1:36669' after 19383 ms
2023-03-30 17:33:43.159 [info] Creating a socket (renderer-Management-d1335990-0980-4a95-9907-b88876400777)...
2023-03-30 17:33:43.160 [info] Creating a socket (renderer-ExtensionHost-533b4b71-9a40-4e19-af77-d5c6b65b0937)...
2023-03-30 17:33:43.872 [info] Creating a socket (renderer-Management-d1335990-0980-4a95-9907-b88876400777) was successful after 713 ms.
2023-03-30 17:33:44.454 [info] Creating a socket (renderer-ExtensionHost-533b4b71-9a40-4e19-af77-d5c6b65b0937) was successful after 1294 ms.
2023-03-30 17:33:45.684 [error] [Extension Host] Error: Error relocating /root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/node_modules/spdlog/build/Release/spdlog.node: _ZSt28__throw_bad_array_new_lengthv: symbol not found
    at Object.Module._extensions..node (node:internal/modules/cjs/loader:1187:18)
    at Module.load (node:internal/modules/cjs/loader:981:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at Function.m._load (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/workbench/api/node/extensionHostProcess.js:125:14199)
    at Module.require (node:internal/modules/cjs/loader:1005:19)
    at require (node:internal/modules/cjs/helpers:102:18)
    at bindings (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/node_modules/bindings/bindings.js:112:48)
    at Object.<anonymous> (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/node_modules/spdlog/index.js:3:35)
    at Module._compile (node:internal/modules/cjs/loader:1103:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1157:10)
    at Module.load (node:internal/modules/cjs/loader:981:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at Function.m._load (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/workbench/api/node/extensionHostProcess.js:125:14199)
    at Module.require (node:internal/modules/cjs/loader:1005:19)
    at require (node:internal/modules/cjs/helpers:102:18)
    at i (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/loader.js:5:98)
    at n.load (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/loader.js:4:1651)
    at _.load (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/loader.js:3:9105)
    at u (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/loader.js:5:9325)
    at Object.errorback (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/loader.js:5:9444)
    at _.triggerErrorback (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/loader.js:3:9399)
    at /root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/loader.js:3:9150
    at n.load (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/loader.js:4:1668)
    at _.load (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/loader.js:3:9105)
    at u (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/loader.js:5:9325)
    at h._loadModule (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/loader.js:5:9453)
    at h._resolve (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/loader.js:6:452)
    at h.defineModule (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/loader.js:5:5548)
    at h._relativeRequire (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/loader.js:5:6172)
    at e (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/loader.js:5:8503)
    at R.C (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/workbench/api/node/extensionHostProcess.js:88:8815)
    at new Promise (<anonymous>)
    at R (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/workbench/api/node/extensionHostProcess.js:88:8795)
    at D.n (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/workbench/api/node/extensionHostProcess.js:88:9925)
    at new D (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/workbench/api/node/extensionHostProcess.js:88:9795)
    at P.m (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/workbench/api/node/extensionHostProcess.js:106:954)
    at P.createLogger (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/workbench/api/node/extensionHostProcess.js:88:5469)
    at new P (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/workbench/api/node/extensionHostProcess.js:91:13841)
    at S.j (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/workbench/api/node/extensionHostProcess.js:84:1296)
    at /root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/workbench/api/node/extensionHostProcess.js:84:3032
    at z.a (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/workbench/api/node/extensionHostProcess.js:66:48073)
    at z.get value [as value] (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/workbench/api/node/extensionHostProcess.js:66:48227)
    at Object.get (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/workbench/api/node/extensionHostProcess.js:84:3438)
    at new u (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/workbench/api/node/extensionHostProcess.js:115:1150)
    at c (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/workbench/api/node/extensionHostProcess.js:125:18641)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
2023-03-30 17:33:46.019 [info] [perf] Render performance baseline is 54ms
2023-03-30 17:33:54.757 [error] Error while registering log channel vscode-remote://attached-container%2B7b22636f6e7461696e65724e616d65223a222f696e7465726163742d6261636b656e642d31227d/root/.vscode-server-insiders/data/logs/20230331T003343/remoteagent.log Timed out while waiting for file to be created
2023-03-30 17:33:54.758 [error] Error while registering log channel vscode-remote://attached-container%2B7b22636f6e7461696e65724e616d65223a222f696e7465726163742d6261636b656e642d31227d/root/.vscode-server-insiders/data/logs/20230331T003343/remoteptyhost.log Timed out while waiting for file to be created
2023-03-30 17:33:55.876 [error] Error while registering log channel vscode-remote://attached-container%2B7b22636f6e7461696e65724e616d65223a222f696e7465726163742d6261636b656e642d31227d/root/.vscode-server-insiders/data/logs/20230331T003343/exthost1/remoteexthost.log Timed out while waiting for file to be created
2023-03-30 17:34:05.989 [info] [remote-connection][ExtensionHost][533b4…][reconnect] received socket timeout event (unacknowledgedMsgCount: 55, timeSinceOldestUnacknowledgedMsg: 20322, timeSinceLastReceivedSomeData: 20323).
2023-03-30 17:34:05.989 [info] [remote-connection][ExtensionHost][533b4…][reconnect] starting reconnecting loop. You can get more information with the trace log level.
2023-03-30 17:34:05.989 [info] [remote-connection][ExtensionHost][533b4…][reconnect] resolving connection...
2023-03-30 17:34:05.990 [info] [remote-connection][ExtensionHost][533b4…][reconnect] connecting to 127.0.0.1:36669...
2023-03-30 17:34:05.990 [info] Creating a socket (renderer-ExtensionHost-533b4b71-9a40-4e19-af77-d5c6b65b0937)...
2023-03-30 17:34:06.465 [info] Creating a socket (renderer-ExtensionHost-533b4b71-9a40-4e19-af77-d5c6b65b0937) was successful after 475 ms.
2023-03-30 17:34:06.484 [info] [remote-connection][ExtensionHost][533b4…][reconnect] reconnected!
2023-03-30 17:34:26.498 [info] [remote-connection][ExtensionHost][533b4…][reconnect] received socket timeout event (unacknowledgedMsgCount: 59, timeSinceOldestUnacknowledgedMsg: 20015, timeSinceLastReceivedSomeData: 20015).
2023-03-30 17:34:26.499 [info] [remote-connection][ExtensionHost][533b4…][reconnect] starting reconnecting loop. You can get more information with the trace log level.
2023-03-30 17:34:26.499 [info] [remote-connection][ExtensionHost][533b4…][reconnect] resolving connection...
2023-03-30 17:34:26.499 [info] [remote-connection][ExtensionHost][533b4…][reconnect] connecting to 127.0.0.1:36669...
2023-03-30 17:34:26.499 [info] Creating a socket (renderer-ExtensionHost-533b4b71-9a40-4e19-af77-d5c6b65b0937)...
2023-03-30 17:34:27.020 [info] Creating a socket (renderer-ExtensionHost-533b4b71-9a40-4e19-af77-d5c6b65b0937) was successful after 521 ms.
2023-03-30 17:34:27.038 [info] [remote-connection][ExtensionHost][533b4…][reconnect] reconnected!
2023-03-30 17:34:47.046 [info] [remote-connection][ExtensionHost][533b4…][reconnect] received socket timeout event (unacknowledgedMsgCount: 59, timeSinceOldestUnacknowledgedMsg: 20008, timeSinceLastReceivedSomeData: 20008).
2023-03-30 17:34:47.078 [info] [remote-connection][ExtensionHost][533b4…][reconnect] starting reconnecting loop. You can get more information with the trace log level.
2023-03-30 17:34:47.078 [info] [remote-connection][ExtensionHost][533b4…][reconnect] resolving connection...
2023-03-30 17:34:47.078 [info] [remote-connection][ExtensionHost][533b4…][reconnect] connecting to 127.0.0.1:36669...
2023-03-30 17:34:47.079 [info] Creating a socket (renderer-ExtensionHost-533b4b71-9a40-4e19-af77-d5c6b65b0937)...
2023-03-30 17:34:47.516 [info] Creating a socket (renderer-ExtensionHost-533b4b71-9a40-4e19-af77-d5c6b65b0937) was successful after 438 ms.
2023-03-30 17:34:47.532 [info] [remote-connection][ExtensionHost][533b4…][reconnect] reconnected!
2023-03-30 17:35:07.536 [info] [remote-connection][ExtensionHost][533b4…][reconnect] received socket timeout event (unacknowledgedMsgCount: 59, timeSinceOldestUnacknowledgedMsg: 20004, timeSinceLastReceivedSomeData: 20004).
2023-03-30 17:35:07.563 [info] [remote-connection][ExtensionHost][533b4…][reconnect] starting reconnecting loop. You can get more information with the trace log level.
2023-03-30 17:35:07.563 [info] [remote-connection][ExtensionHost][533b4…][reconnect] resolving connection...
2023-03-30 17:35:07.564 [info] [remote-connection][ExtensionHost][533b4…][reconnect] connecting to 127.0.0.1:36669...
2023-03-30 17:35:07.564 [info] Creating a socket (renderer-ExtensionHost-533b4b71-9a40-4e19-af77-d5c6b65b0937)...
2023-03-30 17:35:07.991 [info] Creating a socket (renderer-ExtensionHost-533b4b71-9a40-4e19-af77-d5c6b65b0937) was successful after 427 ms.
2023-03-30 17:35:08.006 [info] [remote-connection][ExtensionHost][533b4…][reconnect] reconnected!
2023-03-30 17:35:28.007 [info] [remote-connection][ExtensionHost][533b4…][reconnect] received socket timeout event (unacknowledgedMsgCount: 63, timeSinceOldestUnacknowledgedMsg: 20002, timeSinceLastReceivedSomeData: 20002).
2023-03-30 17:35:28.008 [info] [remote-connection][ExtensionHost][533b4…][reconnect] starting reconnecting loop. You can get more information with the trace log level.
2023-03-30 17:35:28.008 [info] [remote-connection][ExtensionHost][533b4…][reconnect] resolving connection...
2023-03-30 17:35:28.008 [info] [remote-connection][ExtensionHost][533b4…][reconnect] connecting to 127.0.0.1:36669...
2023-03-30 17:35:28.009 [info] Creating a socket (renderer-ExtensionHost-533b4b71-9a40-4e19-af77-d5c6b65b0937)...
2023-03-30 17:35:28.486 [info] Creating a socket (renderer-ExtensionHost-533b4b71-9a40-4e19-af77-d5c6b65b0937) was successful after 478 ms.
2023-03-30 17:35:28.505 [info] [remote-connection][ExtensionHost][533b4…][reconnect] reconnected!
2023-03-30 17:35:48.510 [info] [remote-connection][ExtensionHost][533b4…][reconnect] received socket timeout event (unacknowledgedMsgCount: 66, timeSinceOldestUnacknowledgedMsg: 20005, timeSinceLastReceivedSomeData: 20005).
2023-03-30 17:35:48.511 [info] [remote-connection][ExtensionHost][533b4…][reconnect] starting reconnecting loop. You can get more information with the trace log level.
2023-03-30 17:35:48.511 [info] [remote-connection][ExtensionHost][533b4…][reconnect] resolving connection...
2023-03-30 17:35:48.511 [info] [remote-connection][ExtensionHost][533b4…][reconnect] connecting to 127.0.0.1:36669...
2023-03-30 17:35:48.512 [info] Creating a socket (renderer-ExtensionHost-533b4b71-9a40-4e19-af77-d5c6b65b0937)...
2023-03-30 17:35:48.936 [info] Creating a socket (renderer-ExtensionHost-533b4b71-9a40-4e19-af77-d5c6b65b0937) was successful after 424 ms.
2023-03-30 17:35:48.951 [info] [remote-connection][ExtensionHost][533b4…][reconnect] reconnected!
2023-03-30 17:35:50.869 [info] Electron sandbox mode is enabled!
2023-03-30 17:35:50.888 [warning] Via 'product.json#extensionEnabledApiProposals' extension 'ms-vscode.vscode-selfhost-test-provider' wants API proposal 'testContinuousRun' but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check 'vscode.d.ts') or was abandoned.
2023-03-30 17:35:50.888 [warning] Via 'product.json#extensionEnabledApiProposals' extension 'ms-toolsai.jupyter' wants API proposal 'notebookControllerKind' but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check 'vscode.d.ts') or was abandoned.
2023-03-30 17:35:52.162 [info] Invoking resolveAuthority(attached-container)...
2023-03-30 17:35:52.162 [info] [LocalProcess0][resolveAuthority(attached-container,1)][0ms] obtaining proxy...
2023-03-30 17:35:52.163 [info] [LocalProcess0][resolveAuthority(attached-container,1)][0ms] invoking...
2023-03-30 17:35:53.171 [info] [LocalProcess0][resolveAuthority(attached-container,1)][1008ms] waiting...
2023-03-30 17:35:54.163 [info] [LocalProcess0][resolveAuthority(attached-container,1)][2000ms] waiting...
2023-03-30 17:35:55.163 [info] [LocalProcess0][resolveAuthority(attached-container,1)][3000ms] waiting...
2023-03-30 17:35:56.163 [info] [LocalProcess0][resolveAuthority(attached-container,1)][4000ms] waiting...
2023-03-30 17:35:57.164 [info] [LocalProcess0][resolveAuthority(attached-container,1)][5001ms] waiting...
2023-03-30 17:35:57.668 [info] [LocalProcess0][resolveAuthority(attached-container,1)][5505ms] returned 127.0.0.1:36669
2023-03-30 17:35:57.668 [info] resolveAuthority(attached-container) returned '127.0.0.1:36669' after 5507 ms
2023-03-30 17:35:57.672 [info] Creating a socket (renderer-Management-b41b7be6-b3ca-4db4-9812-44a2646110e0)...
2023-03-30 17:35:57.674 [info] Creating a socket (renderer-ExtensionHost-d2eb0984-8f33-460e-9439-a797a31f7e24)...
2023-03-30 17:35:58.415 [info] Creating a socket (renderer-Management-b41b7be6-b3ca-4db4-9812-44a2646110e0) was successful after 742 ms.
2023-03-30 17:35:59.200 [info] Creating a socket (renderer-ExtensionHost-d2eb0984-8f33-460e-9439-a797a31f7e24) was successful after 1525 ms.
2023-03-30 17:36:00.089 [info] [perf] Render performance baseline is 99ms
2023-03-30 17:36:00.769 [error] [Extension Host] Error: Error relocating /root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/node_modules/spdlog/build/Release/spdlog.node: _ZSt28__throw_bad_array_new_lengthv: symbol not found
    at Object.Module._extensions..node (node:internal/modules/cjs/loader:1187:18)
    at Module.load (node:internal/modules/cjs/loader:981:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at Function.m._load (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/workbench/api/node/extensionHostProcess.js:125:14199)
    at Module.require (node:internal/modules/cjs/loader:1005:19)
    at require (node:internal/modules/cjs/helpers:102:18)
    at bindings (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/node_modules/bindings/bindings.js:112:48)
    at Object.<anonymous> (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/node_modules/spdlog/index.js:3:35)
    at Module._compile (node:internal/modules/cjs/loader:1103:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1157:10)
    at Module.load (node:internal/modules/cjs/loader:981:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at Function.m._load (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/workbench/api/node/extensionHostProcess.js:125:14199)
    at Module.require (node:internal/modules/cjs/loader:1005:19)
    at require (node:internal/modules/cjs/helpers:102:18)
    at i (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/loader.js:5:98)
    at n.load (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/loader.js:4:1651)
    at _.load (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/loader.js:3:9105)
    at u (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/loader.js:5:9325)
    at Object.errorback (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/loader.js:5:9444)
    at _.triggerErrorback (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/loader.js:3:9399)
    at /root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/loader.js:3:9150
    at n.load (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/loader.js:4:1668)
    at _.load (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/loader.js:3:9105)
    at u (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/loader.js:5:9325)
    at h._loadModule (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/loader.js:5:9453)
    at h._resolve (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/loader.js:6:452)
    at h.defineModule (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/loader.js:5:5548)
    at h._relativeRequire (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/loader.js:5:6172)
    at e (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/loader.js:5:8503)
    at R.C (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/workbench/api/node/extensionHostProcess.js:88:8815)
    at new Promise (<anonymous>)
    at R (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/workbench/api/node/extensionHostProcess.js:88:8795)
    at D.n (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/workbench/api/node/extensionHostProcess.js:88:9925)
    at new D (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/workbench/api/node/extensionHostProcess.js:88:9795)
    at P.m (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/workbench/api/node/extensionHostProcess.js:106:954)
    at P.createLogger (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/workbench/api/node/extensionHostProcess.js:88:5469)
    at new P (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/workbench/api/node/extensionHostProcess.js:91:13841)
    at S.j (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/workbench/api/node/extensionHostProcess.js:84:1296)
    at /root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/workbench/api/node/extensionHostProcess.js:84:3032
    at z.a (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/workbench/api/node/extensionHostProcess.js:66:48073)
    at z.get value [as value] (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/workbench/api/node/extensionHostProcess.js:66:48227)
    at Object.get (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/workbench/api/node/extensionHostProcess.js:84:3438)
    at new u (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/workbench/api/node/extensionHostProcess.js:115:1150)
    at c (/root/.vscode-server-insiders/bin/b1ad3f934ca87b76dac5cf3533fb172d1c30e6ba-insider/out/vs/workbench/api/node/extensionHostProcess.js:125:18641)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
2023-03-30 17:36:08.990 [error] Error while registering log channel vscode-remote://attached-container%2B7b22636f6e7461696e65724e616d65223a222f696e7465726163742d6261636b656e642d31227d/root/.vscode-server-insiders/data/logs/20230331T003343/remoteagent.log Timed out while waiting for file to be created
2023-03-30 17:36:08.991 [error] Error while registering log channel vscode-remote://attached-container%2B7b22636f6e7461696e65724e616d65223a222f696e7465726163742d6261636b656e642d31227d/root/.vscode-server-insiders/data/logs/20230331T003343/remoteptyhost.log Timed out while waiting for file to be created
2023-03-30 17:36:11.014 [error] Error while registering log channel vscode-remote://attached-container%2B7b22636f6e7461696e65724e616d65223a222f696e7465726163742d6261636b656e642d31227d/root/.vscode-server-insiders/data/logs/20230331T003343/exthost2/remoteexthost.log Timed out while waiting for file to be created
2023-03-30 17:36:21.124 [info] [remote-connection][ExtensionHost][d2eb0…][reconnect] received socket timeout event (unacknowledgedMsgCount: 61, timeSinceOldestUnacknowledgedMsg: 20368, timeSinceLastReceivedSomeData: 20368).
2023-03-30 17:36:21.125 [info] [remote-connection][ExtensionHost][d2eb0…][reconnect] starting reconnecting loop. You can get more information with the trace log level.
2023-03-30 17:36:21.125 [info] [remote-connection][ExtensionHost][d2eb0…][reconnect] resolving connection...
2023-03-30 17:36:21.126 [info] [remote-connection][ExtensionHost][d2eb0…][reconnect] connecting to 127.0.0.1:36669...
2023-03-30 17:36:21.126 [info] Creating a socket (renderer-ExtensionHost-d2eb0984-8f33-460e-9439-a797a31f7e24)...
2023-03-30 17:36:21.608 [info] Creating a socket (renderer-ExtensionHost-d2eb0984-8f33-460e-9439-a797a31f7e24) was successful after 483 ms.
2023-03-30 17:36:21.626 [info] [remote-connection][ExtensionHost][d2eb0…][reconnect] reconnected!
2023-03-30 17:36:41.630 [info] [remote-connection][ExtensionHost][d2eb0…][reconnect] received socket timeout event (unacknowledgedMsgCount: 61, timeSinceOldestUnacknowledgedMsg: 20004, timeSinceLastReceivedSomeData: 20005).
2023-03-30 17:36:41.663 [info] [remote-connection][ExtensionHost][d2eb0…][reconnect] starting reconnecting loop. You can get more information with the trace log level.
2023-03-30 17:36:41.663 [info] [remote-connection][ExtensionHost][d2eb0…][reconnect] resolving connection...
2023-03-30 17:36:41.663 [info] [remote-connection][ExtensionHost][d2eb0…][reconnect] connecting to 127.0.0.1:36669...
2023-03-30 17:36:41.663 [info] Creating a socket (renderer-ExtensionHost-d2eb0984-8f33-460e-9439-a797a31f7e24)...
2023-03-30 17:36:42.040 [info] Creating a socket (renderer-ExtensionHost-d2eb0984-8f33-460e-9439-a797a31f7e24) was successful after 377 ms.
2023-03-30 17:36:42.064 [info] [remote-connection][ExtensionHost][d2eb0…][reconnect] reconnected!
2023-03-30 17:37:02.073 [info] [remote-connection][ExtensionHost][d2eb0…][reconnect] received socket timeout event (unacknowledgedMsgCount: 63, timeSinceOldestUnacknowledgedMsg: 20009, timeSinceLastReceivedSomeData: 20009).
2023-03-30 17:37:02.099 [info] [remote-connection][ExtensionHost][d2eb0…][reconnect] starting reconnecting loop. You can get more information with the trace log level.
2023-03-30 17:37:02.100 [info] [remote-connection][ExtensionHost][d2eb0…][reconnect] resolving connection...
2023-03-30 17:37:02.100 [info] [remote-connection][ExtensionHost][d2eb0…][reconnect] connecting to 127.0.0.1:36669...
2023-03-30 17:37:02.100 [info] Creating a socket (renderer-ExtensionHost-d2eb0984-8f33-460e-9439-a797a31f7e24)...
2023-03-30 17:37:02.471 [info] Creating a socket (renderer-ExtensionHost-d2eb0984-8f33-460e-9439-a797a31f7e24) was successful after 371 ms.
2023-03-30 17:37:02.487 [info] [remote-connection][ExtensionHost][d2eb0…][reconnect] reconnected!
2023-03-30 17:37:22.494 [info] [remote-connection][ExtensionHost][d2eb0…][reconnect] received socket timeout event (unacknowledgedMsgCount: 74, timeSinceOldestUnacknowledgedMsg: 20007, timeSinceLastReceivedSomeData: 20007).
2023-03-30 17:37:22.525 [info] [remote-connection][ExtensionHost][d2eb0…][reconnect] starting reconnecting loop. You can get more information with the trace log level.
2023-03-30 17:37:22.526 [info] [remote-connection][ExtensionHost][d2eb0…][reconnect] resolving connection...
2023-03-30 17:37:22.526 [info] [remote-connection][ExtensionHost][d2eb0…][reconnect] connecting to 127.0.0.1:36669...
2023-03-30 17:37:22.526 [info] Creating a socket (renderer-ExtensionHost-d2eb0984-8f33-460e-9439-a797a31f7e24)...
2023-03-30 17:37:23.034 [info] Creating a socket (renderer-ExtensionHost-d2eb0984-8f33-460e-9439-a797a31f7e24) was successful after 508 ms.
2023-03-30 17:37:23.051 [info] [remote-connection][ExtensionHost][d2eb0…][reconnect] reconnected!
2023-03-30 17:37:43.057 [info] [remote-connection][ExtensionHost][d2eb0…][reconnect] received socket timeout event (unacknowledgedMsgCount: 74, timeSinceOldestUnacknowledgedMsg: 20006, timeSinceLastReceivedSomeData: 20006).
2023-03-30 17:37:43.088 [info] [remote-connection][ExtensionHost][d2eb0…][reconnect] starting reconnecting loop. You can get more information with the trace log level.
2023-03-30 17:37:43.089 [info] [remote-connection][ExtensionHost][d2eb0…][reconnect] resolving connection...
2023-03-30 17:37:43.089 [info] [remote-connection][ExtensionHost][d2eb0…][reconnect] connecting to 127.0.0.1:36669...
2023-03-30 17:37:43.089 [info] Creating a socket (renderer-ExtensionHost-d2eb0984-8f33-460e-9439-a797a31f7e24)...
2023-03-30 17:37:43.520 [info] Creating a socket (renderer-ExtensionHost-d2eb0984-8f33-460e-9439-a797a31f7e24) was successful after 431 ms.
2023-03-30 17:37:43.537 [info] [remote-connection][ExtensionHost][d2eb0…][reconnect] reconnected!
2023-03-30 17:38:03.537 [info] [remote-connection][ExtensionHost][d2eb0…][reconnect] received socket timeout event (unacknowledgedMsgCount: 75, timeSinceOldestUnacknowledgedMsg: 20001, timeSinceLastReceivedSomeData: 20001).
2023-03-30 17:38:03.564 [info] [remote-connection][ExtensionHost][d2eb0…][reconnect] starting reconnecting loop. You can get more information with the trace log level.
2023-03-30 17:38:03.564 [info] [remote-connection][ExtensionHost][d2eb0…][reconnect] resolving connection...
2023-03-30 17:38:03.564 [info] [remote-connection][ExtensionHost][d2eb0…][reconnect] connecting to 127.0.0.1:36669...
2023-03-30 17:38:03.564 [info] Creating a socket (renderer-ExtensionHost-d2eb0984-8f33-460e-9439-a797a31f7e24)...
2023-03-30 17:38:03.979 [info] Creating a socket (renderer-ExtensionHost-d2eb0984-8f33-460e-9439-a797a31f7e24) was successful after 414 ms.
2023-03-30 17:38:03.998 [info] [remote-connection][ExtensionHost][d2eb0…][reconnect] reconnected!
2023-03-30 17:38:23.997 [info] [remote-connection][ExtensionHost][d2eb0…][reconnect] received socket timeout event (unacknowledgedMsgCount: 88, timeSinceOldestUnacknowledgedMsg: 20000, timeSinceLastReceivedSomeData: 20000).
2023-03-30 17:38:23.998 [info] [remote-connection][ExtensionHost][d2eb0…][reconnect] starting reconnecting loop. You can get more information with the trace log level.
2023-03-30 17:38:23.998 [info] [remote-connection][ExtensionHost][d2eb0…][reconnect] resolving connection...
2023-03-30 17:38:23.999 [info] [remote-connection][ExtensionHost][d2eb0…][reconnect] connecting to 127.0.0.1:36669...
2023-03-30 17:38:23.999 [info] Creating a socket (renderer-ExtensionHost-d2eb0984-8f33-460e-9439-a797a31f7e24)...
2023-03-30 17:38:24.505 [info] Creating a socket (renderer-ExtensionHost-d2eb0984-8f33-460e-9439-a797a31f7e24) was successful after 507 ms.
2023-03-30 17:38:24.523 [info] [remote-connection][ExtensionHost][d2eb0…][reconnect] reconnected!
2023-03-30 17:38:30.853 [error] Error: Aborted onWillSaveTextDocument-event after 1750ms
    at vscode-file://vscode-app/c:/Users/rsuel/AppData/Local/Programs/Microsoft%20VS%20Code%20Insiders/resources/app/out/vs/workbench/workbench.desktop.main.js:1902:13638
2023-03-30 17:38:44.523 [info] [remote-connection][ExtensionHost][d2eb0…][reconnect] received socket timeout event (unacknowledgedMsgCount: 128, timeSinceOldestUnacknowledgedMsg: 20000, timeSinceLastReceivedSomeData: 20001).
2023-03-30 17:38:44.524 [info] [remote-connection][ExtensionHost][d2eb0…][reconnect] starting reconnecting loop. You can get more information with the trace log level.
2023-03-30 17:38:44.524 [info] [remote-connection][ExtensionHost][d2eb0…][reconnect] resolving connection...
2023-03-30 17:38:44.525 [info] [remote-connection][ExtensionHost][d2eb0…][reconnect] connecting to 127.0.0.1:36669...
2023-03-30 17:38:44.525 [info] Creating a socket (renderer-ExtensionHost-d2eb0984-8f33-460e-9439-a797a31f7e24)...
2023-03-30 17:38:45.042 [info] Creating a socket (renderer-ExtensionHost-d2eb0984-8f33-460e-9439-a797a31f7e24) was successful after 518 ms.
2023-03-30 17:38:45.061 [info] [remote-connection][ExtensionHost][d2eb0…][reconnect] reconnected!

About this issue

Original URL
State: closed
Created a year ago
Reactions: 1
Comments: 20 (8 by maintainers)

Most upvoted comments

I have an idea, may be crazy. Why not remove spdlog?

I try to make a fake spdlog, it works fine. Write the code below to vscode/node_modules/spdlog/index.js:

const fs = require("node:fs");
const path = require("node:path");
function Logger(name, filepath) {
  fs.mkdirSync(path.dirname(filepath), { recursive: true });
  const fd = fs.openSync(filepath, "a");
  this.trace = (v) => fs.write(fd, v + "\n", () => {});
  this.debug = this.info = this.warn = this.error = this.critical = this.trace;
  this.getLevel = () => 2;
  this.setLevel = this.setPattern = this.clearFormatters = () => {};
  this.flush = () => fs.fsync(fd, () => {});
  this.drop = () => fs.close(fd);
}
const createLogger = (_1, name, filepath, _2, _3) =>
  new Promise((resolve) => resolve(new Logger(name, filepath)));
exports.createRotatingLogger = (name, filepath, maxFileSize, maxFiles) =>
  createLogger("rotating", name, filepath, maxFileSize, maxFiles);
exports.createAsyncRotatingLogger = (name, filepath, maxFileSize, maxFiles) =>
  createLogger("rotating_async", name, filepath, maxFileSize, maxFiles);
exports.setLevel = exports.setFlushOn = () => {};
exports.version = 11100;

Seems that the usage of spdlog in VSCode is just writing log files, why not choose another pure-js solution? We may need to reconsider the necessity of node-spdlog, this binding is not built with NAPI but using NAN, which needs to be rebuilt after nodejs update.

kkocdko on Apr 13, 2023

The same problem to me. How to fix ?

Emmm… I have gone back to the vscode 1.76 and the problem is gone. Hope to fix it in next release!

dxkrs on Apr 3, 2023

I can confirm: on 1.77 you can no longer have the extensions activated on the Container. Steps: attach VScode to the container No extensions works: no git repo, no lens, nothing with error [error] [Extension Host] Error: Error relocating .vscode-server/bin/.../node_modules/spdlog/build/Release/spdlog.node: _ZSt28__throw_bad_array_new_lengthv: symbol not found

sorinpopescu on Mar 31, 2023

Thank you all for looking into this. It’s rather unfortunate that a patch version in libstdc++ caused major breaking changes downstream. I assume that the reverse case must not have been true, that a lower version of libstdc++ in the build agent did not cause problems for newer alpine containers with a higher version libstdc++, given that there were not any bugs reported.

My personal opinion, not that it has much weight 😃, is that if eventually you will bump your alpine version anyway, it might make sense to not fix this and instead add the information on how to upgrade in the next minor release. Especially, if rolling back something like this causes other problems downstream. Even if you push this off, to another milestone you will still have to deal with bug reports no matter how well you document the change.

raysuelzer on Apr 6, 2023

Verified with the latest Insiders release

Version: 1.78.0-insider (Universal)
Commit: 2c51b3de329d48f45eabe80316f099f46fd3a5cc
Date: 2023-04-26T05:23:57.381Z
Electron: 22.4.8
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: 10.8.168.25-electron.0
OS: Darwin arm64 22.4.0
Sandboxed: Yes

lszomoru on Apr 26, 2023

Thanks for verifying @raysuelzer

deepak1556 on Apr 4, 2023

spdlog and other native modules are now built with node:16.9.1-alpine since https://github.com/microsoft/vscode-linux-build-agent/commit/007bc8f06eeafb5fbe7d3c1d437e519e4696e054 which comes with libstdc++ v6.0.30 whereas the ruby:2.7-alpine3.13 only contains libstdc++ v6.0.28. Also upstream alpine images for node.js binary are built with libstdc++ v6.0.30 https://github.com/nodejs/docker-node/tree/bd6c00f07c5a3b311ce0e346ab69df6b9ef8d08f/16/alpine3.17, so the only solution I can see is for users to upgrade the libstdc++ versions in you containers as mentioned in https://github.com/nodejs/node/issues/41058.

deepak1556 on Apr 4, 2023

The same problem to me. How to fix ? Emmm… I have gone back to the vscode 1.76 and the problem is gone. Hope to fix it in next release!

Out of curiosity are you using a docker container based upon Alpine?

I had this issue with an image based on node:16.13.0-alpine, but no problems with a (Debian-based?) image based on the dotnet 7 sdk. It was resolved by downgrading to version 1.76.

cnicolai-bits on Apr 3, 2023