vscode: The bracket coloriser extension can cause VS Code to become unresponsive
- VSCode Version: 1.46.0
- OS Version: Linux x64 4.9.0-12-amd64
Steps to Reproduce:
- Use VS Code for a while
- Eventually becomes unresponsive, must close the window and reopen.
Does this issue occur when all extensions are disabled?: Yes
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 1
- Comments: 16 (7 by maintainers)
Ok, I have C/C++, Doxygen Documentation Generator, Git History, GitLens, JSON Pretty Printer, Rainbow Brackets, and Tcl installed. I will run today with Rainbow Brackets disabled and report back at the end of the day, that would be enough to prove it because it was happening several times a day.
I swear I tried this with extensions disabled and still got it, but I didn’t run the profile thing with them off. I do have a bracket colorizer, I will try this all again with extensions disabled tomorrow when I’m back in the office to make sure. If it’s just that extension that would be a relief (and I’d be embarrassed about wasting people’s time). I will also get the full list of what I’m running, it’s not much, mostly C++ stuff and a couple other things.
I am also seeing something similar (Debian Sid, codium 1.46.1) The editor window locks up frequently for several seconds after some time using the app, but in my case it will recover.
Looking at the process explorer the only thing that is using CPU at the time is “window” - at 25% which suggests Node.js garbage collector? (I’m on an 8-core system so it could be just pegging one proc).
The window process is using suspiciously a lot of memory for a single tab - memory leak? This never happened before I upgraded to 1.46.