Extension host terminated unexpectedly. #114714
Comments
|
(Experimental duplicate detection) |
|
And the Mac mini with M1 has the issue too. |
|
Can you open devtools and paste the log output from |
deepak1556
added
macos-big-sur
info-needed
|
I have run the Extension:Bisect tool and it has been unable to identify a problematic extension. VS Code Version: Version: 1.52.1 I have attached my console log from DevTools as well. Any ideas? |
|
@phishee from your log the extension host just got a normal exit and not a crash This is usually that some antivirus software tries to kill the process, might want to check on that. |
|
Thanks for the heads-up on the AV. I believe that may be the culprit as I think IT may have installed something new recently. |
|
After upgrading to Big Sur I started to run into this issue as well. I have never seen this issue prior to upgrading. I tried uninstalling and reinstalling all the extensions as well as vscode and still see issues. Here's a screenshot of console.logs I see: System Info: |
|
Having this issue on m1 macbook, happens two or three times over three hours or so, cant put my finger on it but seems to happen when vs code looses focus i.e when i switch to browser and then go back it has crashed. |
|
Having the same issue. Here is a log from the console: Edit Update |
|
just updated my big sur(m1) and also vscode now the extension host crashes silently!! it is very disconcerting when you go to commit your changes and vscode tells you you need to initialise a repository in the current folder. I wounder what would happen if i actually tried? |
|
ahh, I found out how to test the extensions as they are loading, Bracket-Pair-Colorizer-2 was causing the extension host to completely crash out on startup of vscode |
|
@nickstock and others on m1 seeing extension host crash, issue is tracked at #115646. Please follow it for udpates. |
|
As #115646 is closed, I am posting my comment here as I am seeing the same error ("Extension Host Terminated Unexpectedly") I'm using VSCode with Salesforce. Any advice greatly appreciated! Log Info: |
|
@OOOHA can you check if the issue is present with latest insiders https://code.visualstudio.com/insiders |
deepak1556
added
info-needed
|
I have installed Insiders this morning - I will monitor it and see if the crashes still occur. |
|
@derekschinke which platform ? Please paste the output from devtools #114714 (comment) |
|
@deepak1556 The latest version has the problem too. And The same problem occurs on the M1 Mac mini running Mac OS 11.2.2 with the latest arm64 VSCode version. |
|
@OOOHA can you provide the output from devtools console when it happens, also can you attach the crash report following these steps https://github.com/microsoft/vscode/wiki/Native-Crash-Issues#creating-and-symbolicating-local-crash-reports |
|
@OOOHA I ended up having to completely delete everything related to VSCode from my M1 Mac, and then install the latest stable with M1 support. |
|
@derekschinke Which version did you install? |
|
@deepak1556 it says "zsh: parse error near `\n' "but didn't lead me to any folder. |
|
Can you share what you tried ? It should be something like,
|
|
@deepak1556 I ran code --crash-reporter-directory in Terminal. |
Yes that is correct, if the extension host crashes, a report will be generated under the directory you had provided for the |
No matter how many time I tried it always give me the same output "sh: parse error near `\n'". |
|
It seems to be a duplicate of georgewfraser/vscode-tree-sitter/issues/28. |
I just found out by running extension Bisect a lot of times. |
|
hey guys so i was working on vs code one day and suddenly my vscode started giving me extension host terminated unexpectedly and i cant use it correctly and also my live server has stopped working. also it started to happen after i installed node.js i don't know what happened but yea.. ill leave a screenshot down there please help me with anything you can. |
Maybe try the "extension Bisect " |
|
didn't helped it got activated and disabled my two extensions i se prettier and live server, this is the developer tools screenshot, can you please check if you understand anything that is happening from it. |
This is over my ability. |
|
electron/js2c/renderer_init.js:61 The vm module of Node.js is deprecated in the renderer process and will be removed. |
|
man i can't find anything please help anyone it would be appreciated |
|
In the past month I've been getting CONSTANT failures of the extension host. I've tried both the release and the insiders build of VS Code. It's bad enough that I usually can't go for 20 minutes without a failure (!!). And I'm sorry, but I don't have time to pause my day job to fully debug VS Code. Code needs ROBUST, isolated handling of extensions; it really, really, really shouldn't be possible to crash the extension host under any circumstances. A particular extension could die. Sure. Fine. But to crash it so that the entire editor suddenly has no extension functionality? No, not cool. And if something does cause it to crash, there should be telemetry that lets the user know which extension is at fault! And no, I don't have any AV running on my system outside of the built-in Windows Defender, so that's not the issue unless it's something Microsoft itself is doing to kill VS Code. And with people above reporting that they're running zero user-installed extensions, it doesn't seem likely that it's a third party extension issue anyway. From my point of view VS Code has gone from being the most awesome editor/mini-IDE to being absolutely flaky and an embarrassment that I'm feeling I need to apologize for recommending to my team in a matter of a few months. PLEASE put some serious manpower on this problem! If each extension needs to run in a sandbox, or to be otherwise isolated from the rest of the app, then that should be a priority! I've disabled most of the extensions I've used to see if I can track down which of the many extensions I use is causing the issue, but ... extremely frustrated here, especially when after I look I see there are dozens of similar reports dating back months and no actual resolution to the underlying problem. 👎 Sorry for being so grumpy but I hate having an editor that I've been recommending for years suddenly start behaving as if it's
|
|
Killing almost all of the above extensions doesn't help at all. Still saw the extension host failure. Seemingly related: It often dies when trying to debug a Node process with a |
|
@oneshhh @TimMensch the issue you are facing is #125989 please follow it for updates. |
|
@deepak1556 am I reading that issue wrong? It looks like it's a Mac only issue, and I'm on Windows 10. |
|
Sorry I meant to ping @FeDeP2 who had similar trace as #125989 For your scenario, are you able to get crash dumps following the steps at https://github.com/microsoft/vscode/wiki/Native-Crash-Issues#creating-and-symbolicating-local-crash-reports , also what is the output in devtools when the extension host crashes ? |
|
soo i downgraded to 1.52 and it is working fine now but its too buggy |
|
Im on mac OS 10.11, for now just downgrade it, |
|
@farindra is it working all good is the extension crashing again? because i also downgraded to 1.52 but it started the same thing with live server. |
|
@deepak1556 Had a chance to run Bisect, and it isolated Prisma as the problematic extension. And it looks like it's a) a known problem, and b) somehow related to an indirect dependency See the full thread here: prisma/language-tools#786 Still seems wrong that one extension can take down all the others. |
|
All of a sudden this started happening to me out of the blue. Nothing new had been installed on my machine, no Anti-Virus software installed/running. Received an error saying there was no repo and to initialize, but there is 100% a repo. Machine: MacBook Pro (Retina, 15-inch, Mid 2014), 2.2 GHz Intel Core i7, El Capitan 10.11.4 Completely uninstalled and downloaded fresh. Console errors below: electron/js2c/renderer_init.js:61 console.ts:137 [Extension Host] abstractExtensionService.ts:621 log.ts:296 notificationsAlerts.ts:40 log.ts:296 log.ts:290 localProcessExtensionHost.ts:272 |
|
@Crowl3y the issue you are facing is tracked in #125989 and will be fixed in @TimMensch thanks for the follow-up, it is good to know about the problematic extension. As for the design of the extension host, it is better to open a separate issue so that the component owner can talk about it. Since the original report, this issue got side tracked with reports of crashes by other extensions and core. If you are still experiencing extension host crash with latest insiders https://code.visualstudio.com/insiders, please file a separate issue so that it can be looked into. @OOOHA are you facing the original issue with macOS |
|
@deepak1556 It's all good for a long time. |
|
Yup lets do that, thanks for confirming. |
|
@TimMensch I am sorry about the crashes you have experienced. With VS Code's architecture, we have managed to isolate extensions from the core of VS Code, but all extensions execute together in a single process called the extension host process. So a single misbehaving extension can "take down" the entire extension host. This problem has come up multiple times over the years (e.g. #75627 ) and we plan to investigate spawning multiple extension hosts in the future, but this is not an easy undertaking, nor is it clearly the best thing to do. From your post I see that you probably have over 50 extensions. Spawning an extension host process for each of those extensions would cause stutters under Windows (which is notoriously problematic with spawning very many processes quickly) and might eat up a whole lot of RAM. Also, each extension host needs to be managed (events are sent to it, text buffers are mirrored, etc.) by the renderer process, so the overhead for the renderer to keep around 50 extension host processes might be incredibly high. Our current strategy is to create tooling to help you isolate problematic extensions. We automatically profile the extension host when it is not responsive and identify the top executing extension ( |
|
I fixed it! What i did was: I was using the 1.57 version of vs code. The version i'm using now is: https://code.visualstudio.com/updates/v1_54 Works for me, i hope to help someone. |
|
Still, experiencing the same issue in the thread? @vitoneto says have to downgrade to February build is the only solution, why is this happening? |
|
Now i update to the June 2021 (version 1.58). It's working pretty good also! |
|
I still experimenting this. Update |
and others
Issue Type: Bug
I am using Mac OS Big Sur 11.1 with Macbook Pro 2017(intel i5). VScode always pop up the issue"Extension host terminated unexpectedly." especially while I use C++.
VS Code version: Code 1.52.1 (ea3859d, 2020-12-16T16:30:02.420Z)
OS version: Darwin x64 20.2.0
System Info
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
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 (62)
(1 theme extensions excluded)
A/B Experiments
The text was updated successfully, but these errors were encountered: