-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extension causes high cpu load #18
Comments
Are you seeing any actual performance problems that interfere with code editing, or is this just a matter of seeing a high cpu load warning occasionally? The occasional warning is a known issue. |
I have also been getting this pop-up, more so on my laptop (AMD E-350) than on my desktop system (Intel i5-750). For comparison, the i5-750 is 142% better in real-world speed than the E-350, as tested on UserBenchmark For kicks and giggles, I did some digging and was able to get an unminified CPU profile exthost-66300f.cpuprofile.txt which basically shows that the longest time taken is from the still minified Textmate library. I personally feel that this particular issue is more of a lackluster hardware issue than an overrunning software issue because of the nature of parsing code into an understandable context. A possible change to the repo because of this is marking either this issue or #3 as open with the wontfix label(I would recommend this one because it already has an explanation of why it is wontfix). |
Thanks. I'll indeed this as "won't fix". |
I'm having the same problem, it's lagging especially when I try to format (and I have it on every new line and save) and most of the time causes formatters to break or not format at all. Since no issue openers had put their logs, I will put mine in a bit. |
|
Performance
ligatures-limited
1.3.4
Linux x64 5.4.0-45-generic
1.48.2
/home/sruthisudhi/kshetline.ligatures-limited-unresponsive.cpuprofile.txt
Find more details here: https://github.com/microsoft/vscode/wiki/Explain-extension-causes-high-cpu-load
The text was updated successfully, but these errors were encountered: