VSCode - Nordic KConfig extension misbehaviour/excessive CPU/memory usage.

[Zsilet]

Problem - while working in a project where VSCode does not have visibility to the nRFConnect SDK folders, but where the project includes project-specific KConfig files, the KConfig extension seems to be misbehaving as follows:

1. It throws an error into the VSCode output window every 1-2 minutes. This is annoying since it pulls focus from the terminal window even while one is actively interacting with the terminal). 
2. It is using a massive amount of CPU and memory resources (causing computer to freeze pretty often). System monitor shows the underlying python process consuming anywhere from 1-2 GB of RAM at steady state, with spikes up to 5 GB. 

Disabling the extension makes all the performance issues disappear.

This issue seems to have popped up since either the latest version of VSCode or the latest version of the extension. I have had the extension installed for months before this with the same project configuration and have never had any issues.

The issue is seen on an ASUS laptop (ZenBook UX564EI_Q538EI, Intel i7-1165G7 @ 2.80GHz, 16GB RAM), running Linux (Pop!_OS 22.04 LTS).

VSCode version  info:
Version: 1.74.2
Commit: e8a3071ea4344d9d48ef8a4df2c097372b0c5161
Date: 2022-12-20T10:27:19.253Z
Electron: 19.1.8
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: 10.2.154.15-electron.0
OS: Linux x64 6.0.6-76060006-generic
Sandboxed: No

Extension version info: nRF Kconfig v2022.11.50

I am happy to provide any additional details to debug this issue. 

[Zsilet]

Hello Øyvind, 

The issue started happening again today (since 9:22AM when I booted my machine and started VScode, it has now been erroring for more than 6.5 hrs).

The memory consumption is not as bad as it was when I first saw it, but it's still significant. 

I have included the VSCode output logs and a screenshot of the python script's process profile. 

Kconfig_throwing_errors_02062023.txt

 

[Zsilet]

Furthermore, it seems that the memory usage is steadily growing... there may be a memory leak at play here. 

Here is the situation about 24 hours later. At this point my machine is starting to bog down, will need to restart.

[Øyvind]

Hello, 

Zsilet said:

have included the VSCode output logs and a screenshot of the python script's process profile. 

Our VS Code extension team answers:

The user is not using the current VS Code workspace for NCS app development and his configuration does not point to an SDK. Does he expect the extension to provide anything in this workspace?

Have you verified that your workspace is pointing to the SDK?

[Zsilet]

Does he expect the extension to provide anything in this workspace?

I expect/prefer the kconfig extension to be dormant in this deployment. I understand why it cannot perform it's job (as it cannot see the SDK). 

My issue is that the extension interferes with my use of VSCode, specifically by:

1. Using a large amount of system resources
2. Constantly pulling focus from the Terminal window to the Output window (every time it throws another error), making it hard to use the terminal.
3. Causing VSCode to slow to the point that it takes 15-20 seconds just to save a file. 

If the extension were to perform one initial check and then stay dormant till the next time I open the project etc, that would be perfectly acceptable. 

[Øyvind]

Are you able to disable the extension in VS code? Will this stop it using large amount of system resources? You should be able to disable the extension only in that workspace or disable the extension altogether and enable it only in the workspace where you wants to use it.

There is an ongoing internal fix for a similar issue, however, there is not timeline at the moment I'm afraid.