Repository navigation
Insiders on macOS ARM64: Extension Host crashes (SIGILL, EFAULT, EPIPE) #113410
Description
Activity
Possibly relevant, this is also in the developer tools log:
WARN [File Watcher (chokidar)] Watcher is not using native fsevents library and is falling back to unefficient polling.Also these from when
Extension Hostactually crashes:
- changed the title
[-]Insiders on macOS ARM64: `Error: read EFAULT`[/-][+]Insiders on macOS ARM64: Extension Host crashes (`SIGILL`, `EFAULT`, `EPIPE`)[/+]on Dec 25, 2020 One other error I've been seeing in developer tools prior to an
Extension Hostcrash:ERR Request textDocument/codeAction failed with message: Cannot read .eslintignore file: /Users/andreialecu/Work/proj/.eslintignore Error: EFAULT: bad address in system call argument, read: Error: Request textDocument/codeAction failed with message: Cannot read .eslintignore file: /Users/andreialecu/Work/proj/.eslintignore Error: EFAULT: bad address in system call argument, read at /Users/andreialecu/.vscode-insiders/extensions/dbaeumer.vscode-eslint-2.1.14/client/out/extension.js:1:52031 at /Users/andreialecu/.vscode-insiders/extensions/dbaeumer.vscode-eslint-2.1.14/client/out/extension.js:1:52325 at Immediate.<anonymous> (/Users/andreialecu/.vscode-insiders/extensions/dbaeumer.vscode-eslint-2.1.14/client/out/extension.js:1:52690) at processImmediate (internal/timers.js:456:21)New one:
[Extension Host] Error: Illegal argument at Object.t.illegalArgument (file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:50:803) at file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1705:214 at d.invokeFunction (file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1759:614) at u._tryExecuteCommand (file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4214:45) at file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4213:814 (at _executeContributedCommand (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:707:780)) t.log @ /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:336Possibly relevant, this is also in the developer tools log:
WARN [File Watcher (chokidar)] Watcher is not using native fsevents library and is falling back to unefficient polling.Likely relevant for this issue: fsevents/fsevents#349
Robo (@deepak1556) if you need any further information kindly let me know.
I'm curious about one thing
This seems to specify that it's running on node 12, but node 12 isn't compatible with arm64 (at least not the general purpose one). Only node 15 is.
Is this right?
Also, fsevents/fsevents#350 has been merged and pending release as
fsevents2.3.0 which will hopefully happen today, and might help with thechokidarissue.Can you run the arm64 insiders in a new user data dir
--user-data-dir <some-absolute-path>and see if the crash continues.This seems to specify that it's running on node 12, but node 12 isn't compatible with arm64 (at least not the general purpose one). Only node 15 is.
The runtime is patched to work in electron.
Robo (@deepak1556) I ran:
code-insiders --user-data-dir `mktemp -d` .Then had to use
Reload Windowfrom the command pallette due to some issues with extensions.Still got the crash:
(hopefully
Reload Windowdidn't mess with the data dir)
Note that it happens randomly, I've seen it mostly happen when the angular app I'm running in the integrated terminal detects a code change and starts compiling. However, it can happen without any integrated terminal tasks running as well.
What I've been doing and helps a bit, was to run
Workspaces: Duplicate in new windowand run myRun taskthere (which spawns about 3 nodejs processes).It's possible it is related to file change detection though. In this particular crash above, it crashed immediately after saving a file, and when angular started recompiling (running via
ng serve).
Also, at times, this pops up when saving a file and either: a) takes a long time, b) doesn't finish at all (waiting for minutes). I have to cancel it and
Reload Window.While this one was spinning, there was nothing relevant logged in the Developer tools, no warnings or errors.
Attaching the CPU profile of the
vscode.gitwarning, which has been popping up repeatedly.gitintegration definitely seems slow, but not sure if it's git itself being slow or something else.Can you also try to remove the
.vscode-insidersfolder under home directory and see if the extension host crashes.As for the git integration slowdown, its triggered by child_process.spawn calls based on your profile and the root issue is tracked in upstream electron/electron#26143
79 remaining items
this happened again today with SIGILL. It may just be nodejs/node#36826
so out of your control./Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1857 Extension host terminated unexpectedly. Code: null Signal: SIGILLSimon Elliott (@purge) see: #113410 (comment)
The command I was using was:
code-insiders --crash-reporter-directory ~/vscode-crash ..I haven't personally seen any
SIGILLs in a long time, but if they happen frequently for you, it would likely help a lot if you can attach the crash dumps.Reacted by Simon ElliottLately I have seen a crash of the extension host on macOS 11.x ARM almost daily.
Reacted by Karl Horky, Gautier, elyssaDev, Jon Noronha and bl-ueHave we determined that it's memory related? Or is it something like network sockets timing out/disconnecting/becoming invalidated?
Since I posted in April, I have not seen a single extension host crash ever since. I am still using macOS ARM.
Agreed, i have not seen it for months either. not sure whether its was node or macos update that fixed it.
Is anyone in this thread actively experiencing this issue on latest macOS Big Sur 11.4 and VS Code version
1.57.1?Robo (@deepak1556) There has been some activity here nodejs/node#36826 (comment) and a report of a SIGSEGV with the extension host under high memory pressure.
Luckily a nodejs contributor is looking into it, so perhaps we'll have some answers soon.
Personally, I haven't seen almost any crashes in a long time. I use VSCode 8+ hrs per day and in the past 3 months or so I only got one extension host crash or maybe two. (It might still happen more often on a 8GB machine though.)
Edit: just noticed you were involved in that same discussion, and the conclusion was that macOS 11.4 might have fixed it.
Yup I am now looking for users who are hitting this issue on
11.4to validate the nodejs issue findings. I will give this issue some time before closing as fixed.Closing per above comment.
- locked and limited conversation to collaborators
on Aug 26, 2021
Issue Type: Bug
I haven't seen this reported anywhere, so here goes.
Using the latest insiders version on macOS, I noticed that there are stability issues with extensions.
After some time running vscode, the extension host either crashes and needs to be restarted, or the code actions that trigger on saving a document start hanging.
I noticed that in the Developer Tools it frequently logs messages like:
The EFAULT exceptions might be triggering this behavior.
This also hangs and spins forever:
If I cancel it, then run
Developer: Restart Extension Hostit will then save properly.(It's possible one of my extensions might be interfering as well, as I have a ton of them enabled - but I don't remember seeing this on Stable VSCode with Rosetta.)
VS Code version: Code - Insiders 1.53.0-insider (4a875e2, 2020-12-21T12:34:09.548Z)
OS version: Darwin arm64 20.2.0
System Info
gpu_compositing: enabled
metal: disabled_off
multiple_raster_threads: enabled_on
oop_rasterization: enabled
opengl: enabled_on
protected_video_decode: unavailable_off
rasterization: enabled
skia_renderer: disabled_off_ok
video_decode: enabled
webgl: enabled
webgl2: enabled
Extensions (58)
(2 theme extensions excluded)
A/B Experiments