TSServer consume constant CPU load (~10% or even more) also I am not typing or doing anything in VS Code

[dbaeumer]

See attached screen shot.

This is with having the VS Code workspace open

[dbaeumer]

Version 1.24.0-insider
Commit f67e639
Date 2018-06-04T20:56:48.515Z
Shell 1.7.12
Renderer 58.0.3029.110
Node 7.9.0
Architecture x64

[dbaeumer]

Some more testing:

• After I start the CPU load after some initial computation goes down to 0%
• I don't know exactly when but after some time the tsserver never goes beyond 10% CPU consumption for a longer period of time (> 5 seconds) even if I have VS Code in the background
• I do start scripts\code if that makes a difference and I have npm run gulp watch running

[dbaeumer]

Same happens with

Version 1.23.1
Commit d0182c3
Date 2018-05-10T17:11:17.614Z
Shell 1.7.12
Renderer 58.0.3029.110
Node 7.9.0
Architecture x64

[dbaeumer]

I could now reproduce this by simply starting code opening task.contribution.ts and then let it sit for a while.

[dbaeumer]

I tried again and this time it didn't reproduce. So it is not consistent but if it happens then the impact it quite noticeable on the CPU. Anything you want me to do to help tracking this down?

[mjbvz]

I haven't been able to repo this using those steps. Let me try on windows too though.

Can you please check the tsserver log to if it says that anything is happening during the periods of cpu usage

[dbaeumer]

Will do.

[dbaeumer]

Here is the server.log. I noticed high CPU load at the end of the session (around 13:34). The interesting thing is that the tsserver watches for file changes that are totally unrelated to any project info.

tsserver.log
ti-16276.log

[sheetalkamat]

I think the root cause for this is microsoft/TypeScript#24471 where in we aren't ignoring writes in some cases. This would repro only for classic module resolution. Working on fixing this.

Edit actually microsoft/TypeScript#24471 isn't in the vscode insiders drop

[mjbvz]

@dbaeumer Can you please test this with TypeScript@next as well?

[sheetalkamat]

@mjbvz @dbaeumer The issue here is location of vscode folder in "c:/users/username/Projects" folder. We ignore "/users/username/Projects" and "c:/users/Projects" kind of pattern but not that one. I am working on the fix. Thanks.