Apple silicon(m1) version run node cause err: Extension host terminated unexpectedly

[vast-z]

• VSCode Version: insider(apple arm experience)
• OS Version: mac os big sur

Steps to Reproduce:

1. write a js script
2. press F5 run with Nodejs,then cause this error

Does this issue occur when all extensions are disabled?: Yes.

[weinand]

/needsMoreInfo

[weinand]

Please provide reproducible steps:

• How does the JS program and your launch.json look like?
• Screenshot of the error.

[vast-z]

Thank you very much for your reply. After I restart vscode, "Extension host terminated unexpectedly" will no longer pop up in the lower right corner, but the js program still cannot be executed, auto exit. It also cannot be used for debugging. The terminal is running well.

[connor4312]

Can you collect some logs? That should show us the complete error which is truncated in the call stack view.

/jsDebugLogs

[vast-z]

Thank you very much for your reply. Is this the debug information?

[connor4312]

Indeed, unfortunately not many more details there

Error: hash.bundle.js process unexpectedly exited
at t.Hasher.send (extension.js:22:34881)
at t.Hasher.verifyFile (extension.js:22:34710)
at Object.t.checkContentHash (extension.js:1:58595)
at new I (extension.js:1:61505)
at F.addSource (extension.js:1:69494)

I don't have an Apple Si device to test on but will see if I can find one to remote into

[vast-z]

thank you for your help. If necessary, I can provide the device remotely for debugging..

[connor4312]

This looks like https://bugs.chromium.org/p/chromium/issues/detail?id=1150060 -- we use wasm in several areas in the debugger, including the hash.bundle.js. Source map parsing using wasm as well and happens in the main thread, which is why you might be seeing a crash there.

[richiksc]

This might have been fixed by nodejs/node#35986. Many people were reporting issues with wasm causing crashes on Apple Silicon, V8 released some fixes, and Node cherry-picked them and merged them into master on Nov 12. They haven't published these changes as a release yet, however, even as of v15.2.1 which was released on November 16th. VSCode could either wait for an upstream release or cherry-pick these changes from upstream Node for the debugger.

Edit: this issue nodejs/node#36160 pointed me to the aforementioned pull request, because they also mentioned wasm as the source of their test failure.

[vast-z]

I found that in the latest version, this problem seems to have been solved, thank you very much for the people who worked on this

[deepak1556]

Yes latest update a31f124 with newer electron runtime 11.0.3 fixes loading of wasm modules. Thanks for confirming.