Thanks a lot for your feedback.
If you look at the background processes in Windows, you should see 2 processes started by SonarLint:
- a Java process
- a nodejs process
You can see on my side that memory consumption is acceptable, after analyzing a few JS/TS files.
Would you be able to determine which one of the two processes is consuming CPU/memory?
Does the CPU/memory consumption occurs immediately after starting VSCode and opening a single file, or only after some time of work (opening multiple files, changing code). I would like to understand if the problem is specific to your project or hardware, or if we have a memory leak.
Another thing you can try is to enable verbose and analysis logs in VSCode settings:
Then open and clear content of the SonarLint output:
And finally open a source file you know will make your CPU burn. Watch log output, trying to determine at which step it is taking time.