High CPU usage / Intellisense stops working #16073
Comments
|
@MoxxNull Can you reproduce without having extensions enabled (start code with |
|
By the time I posted that, I realized that shoul have been the first thing to do, sorry.. I am currently running without extensions, in case that goes well I will add one by one. I'll add more info ! |
|
I have the same problem. The program stops working and then, just freezing, so I have to kill the program and reopen all the programs. I recently updated the program and today, I have been trying to solve this problem. Come on! Help! |
|
I'm running into a similar issue on OS X El Capitan (case-sensitive filesystem) while working on a TypeScript project. After noticing IntelliSense stop working (specifically, mousing over something to get its type and/or documentation hangs indefinitely), I consistently find a process called Code Helper spiking my CPU above 100% until I kill it from the task manager. Only extensions I have installed are Microsoft's "Docker Support" and "Git Blame". |
|
@buu700 @Jussif @MoxxNull did you have at some point Crane installed on VS Code ? I ran into the same problem last week. My VSCode started to consume a huge amount of CPU and Code Helper was taking 120% CPU. Even though I had Crane uninstalled it didn't change. I had to close Code and kill the process. |
|
Nope, haven't used that one, although it's possible that I could've installed another extension with a similar issue at some point. |
|
Me neither.. Still testing it without extensions / adding one by one. So far it seems good, but as the problem appeared after several hours this will take some time. |
|
I don't have installed that program. I only have one extension that is the python extension created by donjayamanne. Yesterday, I realized that VS Code consumed more than 50% of the CPU memory and I tried to find the Code Helper process but I didn't find it. How do you find this process on the pc @MoxxNull @fbnlsr @buu700??? Thanks for your help |
|
If multiple people are having this problem, just post your list of extensions and we can narrow down the common denominator that way. Any easy way to list all active extensions? |
|
@method-x I have only one extension installed on VSCode. This extesion is PYTHON created by donjayamanne. "python.devOptions":["USERELEASEAUTOCOMP"] As soon as I have results I will notify you. Thanks for your help. |
|
@method-x You can use |
|
I have been working adding this command line without any problem. "python.devOptions":["USERELEASEAUTOCOMP"] After this correction, the VSCode is working correctly without increasing the PC usage @DonJayamanne . |
chrmarti
added
the
*duplicate
|
Well, I can at least confirm this is an extension issue. I uninstalled a few extensions I wasn't using and haven't had this issue since. I didn't keep track of the extensions I uninstalled. |
|
Agreed that it's probably an extension issue. While I have still had IntelliSense randomly die on occasion since removing my git blame extension, it hasn't been nearly as frequent or been accompanied by the high CPU usage of the original issue. |
|
Not sure if it's the same root cause or an entirely different issue, but I've been running into exactly these symptoms again (with no extensions enabled) since the 1.8.1 update. |
|
@buu700 Could you run the command in #17740 (comment) when the problem occurs and paste the result there? |
A bit more information:
|
chrmarti
added
bug
|
Reopening for the tsserver using a full CPU and staying around after closing the application. Over to you @mjbvz. |
mjbvz
added
the
freeze-slow-crash-leak
waderyan
changed the title
|
Any updates on this? It's still reproducible with 1.9. Also, just went ahead and tested with vscode versions 1.4 - 1.6, and it's consistently reproducible in all of them despite my never having run into this (to my knowledge) before 1.7. Is it possible that this could be a bug in an external dependency, e.g. tsserver being referenced from my global node modules rather than from the vscode bundle? |
|
Could we have an update on this? I have started experiencing it consistently since the 1.9 update, exact same symptoms. I have also talked to at least 3 others who are also getting it since 1.9 |
|
I can't guarantee that this is happening since 1.9, but it definitely happens since some time. Intellisense suddenly stops working, CPU usage rises to ~15% from roughly 0-1% before and the ram usage spiked to over 800MB from roughly 150MB (just the highest using process, not all combined). [email protected] |
|
Can you reproduce this problem if you disable all extensions? But I thought that the problem in the editor, because I see a lot of such messages. |
|
@mrmlnc Just tested this, disabled all extensions, been coding for about an hour doing a node.js application in TS and now my intellisense is 100% gone, all TS support is gone, CPU is sitting at a constant 34% (on a quad core i5). This is on a windows 10 machine |
|
I finally found a workaround for this! Looks like it's unrelated to extensions; I just added a jsconfig.json with |
|
@buu700 It sounds like you were running into microsoft/TypeScript#14636. We've added a workaround in VSCode 1.12 to limit how often this should be hit Please give VSCode 1.12 with TS 2.3.2 a try a let me know if you are still hitting this issue. Another possible cause is microsoft/TypeScript#15301 which we are still looking into |
|
Awesome, I'll update and test it out; looks like I'm currently running 1.11. |
|
Yep, can't reproduce the problem with the insiders build. Terrible time for me to finally find a workaround after dealing with this for so long, but glad it's finally properly resolved! |
|
I also have a problem with intellisense when I use graphql because AST type guide is too long to reproduce
|
|
It's much more infrequent now, but I have still been occasionally running into these exact symptoms (Code Helper processes hanging around after vscode is closed and using high CPU). |
Steps to Reproduce / Problem:
The text was updated successfully, but these errors were encountered: