Extension Host keeps crashing
See original GitHub issueIssue Type: Bug
After the last update to 1.36.1 of vscode I started to have the Extension Host failing and crashing every while and then, that’s at least once every 2 hours. I’ve never had this behaviour before. The console has the following error with every crash:
Error Python Extension: 2019-07-14 07:06:06: Failed to parse interpreter information for 'C:\Users\USER\AppData\Local\Microsoft\WindowsApps\python.exe' with JSON Python was not found but can be installed from the Microsoft Store: https://go.microsoft.com/fwlink?linkID=2082640 [SyntaxError: Unexpected token P in JSON at position 0 at JSON.parse (<anonymous>) at p.getInterpreterInformation (C:\Users\abdul\.vscode\extensions\ms-python.python-2019.6.24221\out\client\extension.js:75:287807)]
t.log @ workbench.main.js:sourcemap:240
Extension version: 2019.6.24221 VS Code version: Code 1.36.1 (2213894ea0415ee8c85c5eea0d0ff81ecc191529, 2019-07-08T22:59:35.033Z) OS version: Windows_NT x64 10.0.18936
System Info
Item | Value |
---|---|
CPUs | Intel® Core™ i7-6650U CPU @ 2.20GHz (4 x 2208) |
GPU Status | 2d_canvas: enabled 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 |
Load (avg) | undefined |
Memory (System) | 15.93GB (7.76GB free) |
Process Argv | –file-uri file:///d%3A/devel/limp/limp.code-workspace |
Screen Reader | no |
VM | 0% |
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:14 (1 by maintainers)
Top Results From Across the Web
Extension host keeps crashing on Big Sur #113817 - GitHub
Extension host crashes are in >90% of the times caused by one of your installed extensions. All extensions execute together on a single...
Read more >How do I determine which VS Code extension is causing a ...
When the extension host crashes, you should get a popup window that asks to debug the process or restart the extension ...
Read more >Use Visual Studio Code SSH without crashing your server
The solution is to disable the automatically enabled, totally hidden, idiotic TS/JS Language Service extension which installs and runs massive node processes on ......
Read more >Extension Host - Visual Studio Code
The Visual Studio Code Extension Host is responsible for managing extensions and ensuring the stability and performance of Visual Studio Code.
Read more >.NET Generic Host - .NET | Microsoft Learn
Exit . Environment.Exit isn't a graceful way of shutting down a process in the Microsoft.Extensions.Hosting app model. It raises ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks for the info. Every person with ‘Extension Host keeps crashing’ sort-of issue can have extension crashing for different reasons. So closing this, feel free to report with a new issue if you face it the next time.
So, I dumped this issue for a while when I started to see decreased number of crashes occurring until it’s almost gone. Not entirely sure, but I’ve spent the last week way more relaxed with almost no crashes of this kind.
I don’t know what to attribute this for, but I had much of plugins enabled and almost disabled all of them, which bring me to think this could be an issue related to overuse of the extensions with vscode. However, I’ve never at any given time stopped Python extension, so it’s safe to assume it has nothing to do with it.
I’m keeping this opened as I see another person reporting the same issue, however if required it can be closed.