"Extension host terminated" Crash Again on Startup (for Yet Another Extension) + Errors Fail to Get Logged + Unable to Determine Extension Causing #80165
Comments
|
(Experimental duplicate detection)
|
|
Hi @PowerAccess I just had the same problem, I disabled "Angular console" and it started to work again. |
|
Thanks for the tip.
I've had to disable a few which all seem to cause the issues. And some
which seem to fix when I do come back later. It's never clear which are the
cause or if it's a new one now causing the issue.
I believe this needs to be fixed in the Extension Host / VSCode core vs per-extension temporary workarounds.
|
|
Here is what I can piece together from your issue. From your dev tools screenshot, the extension host process crashes with the exit code From the extension host log, the extension host (at the time of crashing) has code executing from the following extensions: Do you have any steps that reliably reproduce the crash? |
|
I had Extension Host crashed yet again today on startup. There are no steps that can be taken to forcibly reproduce this. It occurs seemingly randomly, every few days, whether or not opening VS Code in the same way and performing the same steps. It will only occur once on a day it occurs. It will not occur again until a few days later. And despite opening under the same conditions for the same file or type of file, and only if I leave it open for about a minute or so at least. Considering this, I suspect it may relate to extensions being updated. The only common entry I noticed for extensions that were being updated was the following found in sharedprocess.log for the crash today and the previous crash, respectively. According to the Visual Studio Code Live Share extension releases page on GitHub (https://github.com/MicrosoftDocs/live-share/releases) (unlike the published Changelog on VS Marketplace which is rarely updated: https://marketplace.visualstudio.com/items/MS-vsliveshare.vsliveshare/changelog), this crash occurred within a few days of the Live Share extension update being a released, in each case. This time I just opened VS Code directly instead of using to open a .md file like last time. However, I noticed that it auto opened an unsaved workspace and it may or may not have done so last time as well. I noticed that "sharedprocess.log" always ends with the following line (followed by an empty line): This crash occurred despite my having disabled the following extensions (known to sometimes cause these crashes) a number of days prior to this having occurred.
I will now try disabling "Live Share" extension and see if ends crashing the extension host on startup still, and fails to prevent it after the next Live Share extension release occurs, as I suspect it might be related to Live Share extension being updated. |
Logs for New Crash TodayFor the new extension host crash that occurred today, I have included Debug Console screenshot and copy-pasted text as well as a zip file which includes the logs/ subfolder as well as a few other files such as operation_log.txt and the exthost-d3aade.cpuprofile file it references. Different Error Code for New CrashIn this case there is a new error shown: However, that occurs after the extension host crash, and didn't show up in any of the many other crashes cases previously, from what I recall. In this case, extension host crashed with a different exit code of 3221225477 (which I believe is 0xC0000005 for "Access Violation"). Yet another generic error code, and not even consistent in which one occurs. For reference, this crash occurred at 12:44 PM (or possibly 12:45 PM) 9/9/2019 PDT, within a minute of opening VSCode. Debug Console Screenshot for New Crash
Debug Console Text for New Crash[abhiagr.livs]: Command (Many more similar "[Violation] Added non-passive event listener " omitted here). |
How to Get More Details with Error Missing In Log FilesIn what log files can I look to find "_onExtensionHostCrashed" and the exit code you had mentioned or any kind of details regarding the extension host crash? Will enabling "Preserve Log" in Console help ensuring logging to files? Is there an additional dump / crash report I can generate or locate when this next occurs that will be helpful? Is there any way to enable more details to be logged about these crashes such as with additional logging options enabled? It seems absurd that there is no way to identify which extension might be running code that could cause the crash, due to lack of isolation or otherwise, especially when allowing extensions to run native code. Also, is there a way to enable Time Stamps to be shown in the Dev Tools or in whatever log file (if any) the Extension Host crash, etc. log entries might be able to be output to? |
Live Share Extension Update Seems to Cause the Extension Host CrashAs detailed in my previous comment, it seems that the Visual Studio Code Extension Host crashes during or immediately after updating the Live Share extension. However, the Live Share extension activation doesn't actually appear in the exthost log file, only the updating does. Other References to Extension Updates (eg. with Live Share) Causing Host CrashOther references to Live Share (or Live Share Audio) causing Extension Host crashes after being updated:
According that 3rd related report, this issue isn't even planning to be addressed any time soon from the extension developers (possibly because it seems to be a reoccurring issue, with many reports going on for some time now, as described in #79782) No Live Share Extension Activation In LogThough it seems like the most recent cause of VSCode Extension Host crash is when Live Share extension gets updated, there doesn't seem to be any activation in the exthost log file. Possible CausesConsidering that, it seems like either: A. The crash prevents the activation from getting logged In either case, it seems like something that may need to be addressed in core VSCode vs. extension-specific fixes, especially since, from what I'd reported in #79782 (with links to other related issue reports for various extensions), this issue keeps reoccurring for extensions once fixed temporarily. Extension Activation and Errors Not Found in Logs (Making Nearly Impossible for Users to Identify and Disable Even as a Workaround)Also, the extension causing the crash doesn't appear in logs (for its activation or any extension-specific logging or otherwise, at least not beyond log entries for updating it), making this even harder to identify and fix what is causing it, and making it impossible for users to determine and disable the extension causing this to get VSCode to stop crashing on startup many of the times they launch it (especially since can't even just try disabling one-by-one to determine by process of elimination since doesn't occur on every startup, as mentioned in #79782). Extension Timing or Dependency Issues?Also, I'd seen mention in some related reports of this possibly being related to inter-dependencies between extensions or timing issues related in updating and/or activating them. Reliability & Logging Improvements/Fixes in VS Code Core/Extension HostAre there changes that can be made to fix the underlying cause or minimize the frequency of Extension Host crashing, or at least to enable logging which extension is likely to be the cause, as well as to log the extension host crash itself to files (which as mentioned seems to be missing from any logs saved to disk), and to auto-restart the extension host (vs. always prompting the user to do so) when does repeatedly occur. I'd summarized in #79782 a few specific suggestions related to that, based on a review of many related issue reports across different extensions. Extension IsolationAlso, is Extension isolation, like I'd proposed in #52116 (along with details on some options and projects that may be able to help provide support for that, as has been used successfully with Electron-based applications, and as I'd suggested in #79782 how that could help with reliability even more than security) something that could be considered as well? |
|
From the latest crash, here are the extensions that were loaded: Latest extensions activatedHere are the extensions that were running code in the extension host for both crashes: What I find interesting is both log files end abruptly with
There is no yielding or any undeterministic calls in between those two log statements, yet by looking at the log file, it appears the crash occurs in between them, which I cannot really imagine... |
|
@alexandrudima In most recent crash in sharedprocess.log In the crash before that in sharedprocess.log Therefore it seems like the crash may occur whenever Live Share extension gets updated, occurring once until the next time it's updated. Also, in what log file, if any, should the extension host termination error be found? |
|
I'd referred to a few issues where others reported Extension host terminating when Live Share or Live Share Audio extension (or update) installation occurs, with install/updating failing to complete successfully with failure to install binary dependencies. Those include: |
Flush happens at an interval of 500ms. It also flushes when the log service is disposed. Since it is a crash here I assume that last log statement would have been not written. |
|
@sandy081 Is there a way to execute such that we flush after each log statement? Because otherwise we never know what really happens in case of crashes. |
|
Related #79116 |
|
This problem bother me for a long time....... The VS code's extension host will crush when startup and be recovery after restart the host several times. It would be more better if we can get the info of which of the extension cause this by the console. |
|
BTW, the problem seems occurs after I install a series extensions of MS Remote but I'm not sure about that. |
|
Though the frequency seems to reduce after disabling the VS Live Share extension, I just got another Extension Host terminated crash on startup again despite that, with another extension. Related to Extension Updates or Language Packs?Is there any chance this may be related to install/updating of extensions more than activation of them? And, as seen in the 2nd screenshot of Console Log which is shown after I opened a .txt file in VS Code after the crash occurred, there are a number of errors related to missing language packs and I had seen some of those in the log files for logs that occurred before the crash too. Screenshots
Log Files.zip of logs folder + an operation_log.txt also found under
Console Errors
Additional Errors after CrashI also found the following errors shown after the Extension Host crash during that same sessin as soon as I opened a .log text file in VS Code (as no file was opened when launched VS code), which I wonder if relate to language pack registration/clean/updating/installation?
|
|
I tried to diasble the Live Shared from MS. |
|
@PowerSheetAI We now can trust our logging (because we flush after each log statement). Does the crash still occur for you? |
|
This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines. Happy Coding! |
Issue Type: Bug
I opened a .txt file with VSCode on Windows 10 x64 and Yet again VS Code started up with "Extension host terminated" occurring within seconds of launching it, even when just using VSCode to open a text file. And this occurs randomly, even when trying the same test file. And occurs with failed logging of the errors and with many different extensions, including official ones, which seems to be the cause in different cases, seeming to indicate core VSCode or Extension Host issues more than extension-specific issues.
"Extension host terminated" Screenshot
Related Issue Detailing Trend of Increasing number of Extension host termination errors across many extensions
See #79782 for more details and overview of series of related bug reports, regarding this being a common issue that keeps reoccurring for many popular extensions and how it is impossible to determine which extension caused it and how the crash error itself and the error that caused it or even the extension activation that caused it, it seems, are failing to get logged, as occurred in this case as well.
I submitted this crash report to provide more details, log files and the like to use as a key test case for debugging and fixing the widespread VSCode issue which I'd described in #79782.
Failed Logging and Crash Timing
The crash occurred within seconds or less than 1 minute of launching, so around 3:06 PDT 8/31/2019.
I waited until around 3:12 PM to perform "Show Developer Tools".
I expanded all items in the Developer Tools with all levels shown and then saved the log file. Only in that log file does "terminated" or "onExtensionHostCrashed" show up. No were under any log file under any folder under C:\Users\Dan\AppData\Roaming\Code\logs\ does either of those words occur when searching all files there.
In fact, no errors of any kind (which occur only during Extension Host Crash sessions) show up in any of the log files for any of the folders created under that path.
This occurred again, 6 days later, after my last related bug report regarding this, despite having disabled other extensions known to cause such issues. Due to lack of error messages getting logged, or even it seems the related extension activation getting logged in time when the host crashes, combined with the fact that I have hundreds of extensions enabled and that this crash does not occur every time I startup VSCode, means that it is impossible to determine which extension caused it.
It seems like this may relate to a timing or extension update/activation/interdependency issue, as detailed in #79782, which needs to be addressed in code VSCode or Extension Host code instead of being any specific extension or something that can be fixed or worked around reliably by any extension. Even core Microsoft official extensions like Live Share Audio are aware but have mentioned they are unable to fix any time soon and others who are aware of it and have fixed it but keep having the issue reoccur despite this temporary workarounds. And there are 800+ bug reports across various extensions regarding this issue, recently, as all detailed in #79782.
Errors in Developer Tools
These errors are only shown in Developer Tools. No time stamps. And they do not appear on any of the log files on disk, as detailed above. Also, the issue reporter was unable to gather/submit this.
Developer Tools Saved Log File
Though the log folder doesn't show the error, I saved this log file from Developer Tools (after I enabled all Log Levels, manually expanded each log entry, and then saved to file) which at least shows the crash error (only place shown, not logged to disk anywhere, and only shown if show Dev Tools or Restart Extension Host I believe), plus associated zipped log folder (which fails to include that or any other error related to the crash it seems).
ExtensionHostCrash-SavedFromDevTools-1567289793429.log
20190831T150524-crashed-again.zip
Same Log Folder after Opening Dev Tools and Closing VSCode (to see if error logging is getting delayed after DevTools is shown)
Non-Crash Logs for Comparison
For comparison as a control case, here is a log file I had saved from Dev Tools (also after expanding all items, with all log levels enabled) and the associated zipped log folder, created during a session right after the crash.
StartupOK-AfterCrash-SameFileOpened-FromDevTools-1567292042652.log
20190831T155210-no-crash-right-after.zip
For that 2nd case, I had launched VSCode the same way (opening the same .txt file) and waited a minute for all extensions to load, which happened fine, without any crash. This shows how this may be some kind of timing related or seemingly randomly occurring issue with the Extension Host, not something that reliably occurs due to one broken extension. Also, due to failed logging issues, this may help you to identify what extension might have caused the crash by what extension activations, etc. occurred after logging had stopped during the crash case.
The below zipped log folder is from a session about 1 hour prior to the one where the crash had occurred. This may help identify if there is some issue related to leftover/deferred to next startup/incomplete extension updating for example, considering what seemed to be some of that occurring in the log files.
Many Empty Log Folders Being Created and Left Over
Strangely, like shown in the below screenshot of File Explorer, there were 6 empty log folders (which keep getting created and never cleaned up) which were created before I closed VSCode since the log folder first created on VSCode startup for this crash session.
You might want to also consider fixing that as well. With auto-cleanup or preventing those empty log folders from being created in the first place, as they make it hard to find the needed log files. Also, they might indicate some other issue with logging failing to occur.
My Platform and Configuration
VS Code version: Code 1.37.1 (f06011a, 2019-08-15T16:17:55.855Z)
OS version: Windows_NT x64 10.0.18362
Extensions Enabled and System Info from Issue Reporter
System Info
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: disabled_software
oop_rasterization: disabled_off
protected_video_decode: unavailable_off
rasterization: enabled
skia_deferred_display_list: disabled_off
skia_renderer: disabled_off
surface_synchronization: enabled_on
video_decode: enabled
viz_display_compositor: disabled_off
webgl: enabled
webgl2: enabled
Extensions (166)
(1 theme extensions excluded)
The text was updated successfully, but these errors were encountered: