Extension host frozen with large document
See original GitHub issue- have this setting
"typescript.tsserver.log": "verbose"
- open the TS server log
- in another editor request intellisense
- 🐌 the extension host will be slow, blaming this extension for taking up for then 5 seconds CPU time

GitHub.vscode-pull-request-github-insiders-unresponsive.cpuprofile.txt
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
VSCode Python Extension: Extension host terminated ...
Everything was working fine until Yesterday when my Python extension gave me this error "Extension host terminated unexpectedly" and I'm unable to run...
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 >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 ...
Read more >User Guide - Cold Turkey
Click the install button for each browser to install the extensions and then follow ... Then on Windows, make the C:\Windows\System32\drivers\etc\hosts file ......
Read more >"Although GNOME Shell integration extension is running ...
Ubuntu 22.04 forces the Firefox Snap default for everyone, across every flavour. Sadly the Snap version of Firefox in Ubuntu 22.04 won't ...
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 Free
Top 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
300 might be a little strict, I think 10000 should still do it. We might also come up with something smart here https://github.com/microsoft/vscode/issues/95319 and it might resolve this issue after all
Very nice, I will remove it!