addon-vscode

addon-vscode copied to clipboard

I see high cpu load since the last update. It was not using too much cpu before. After the start of this addon, cpu usage goes up to 80-90% without opening anything, just loading the web interface. High cpu usage remains after closing the web interface and keep running it.

Having the same issue. Raspberry Pi 4 reports very high RAM usage, too. Device gets very toasty. Have to disable the addon until fixed.

Similar issue, seeing CPU and mem increasing while addon is running, once it gets into the 90's the system starts becoming unresponsive.

Nothing abnormal in the logs:

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting

-----------------------------------------------------------
 Add-on: Studio Code Server
 Fully featured Visual Studio Code (VSCode) experience integrated in the Home Assistant frontend.
-----------------------------------------------------------
 Add-on version: 5.15.0
 You are running the latest version of this add-on.
 System: Home Assistant OS 11.4  (amd64 / generic-x86-64)
 Home Assistant Core: 2024.1.5
 Home Assistant Supervisor: 2023.12.1
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-timezone: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
[11:53:05] INFO: Configuring timezone (Australia/Adelaide)...
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service base-addon-timezone successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-user: starting
s6-rc: info: service init-mysql: starting
s6-rc: info: service init-mosquitto: starting
s6-rc: info: service init-code-server: starting
s6-rc: info: service init-code-server successfully started
s6-rc: info: service init-mysql successfully started
s6-rc: info: service init-user successfully started
s6-rc: info: service code-server: starting
s6-rc: info: service code-server successfully started
[11:53:05] INFO: Starting code-server...
s6-rc: info: service init-mosquitto successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[2024-01-26T01:23:06.008Z] info  Wrote default config file to /root/.config/code-server/config.yaml
[2024-01-26T01:23:06.351Z] info  code-server 4.20.0 d0215eca8804d0be5d3551c39404e336032c3141
[2024-01-26T01:23:06.352Z] info  Using user-data-dir /data/vscode
[2024-01-26T01:23:06.366Z] info  Using config file /root/.config/code-server/config.yaml
[2024-01-26T01:23:06.366Z] info  HTTP server listening on http://0.0.0.0:1337/
[2024-01-26T01:23:06.366Z] info    - Authentication is disabled
[2024-01-26T01:23:06.366Z] info    - Not serving HTTPS
[2024-01-26T01:23:06.366Z] info  Session server listening on /data/vscode/code-server-ipc.sock
[11:53:34] 




[11:53:34] Extension host agent started.
File not found: /usr/local/lib/code-server/lib/vscode/out/vsda_bg.wasm
File not found: /usr/local/lib/code-server/lib/vscode/out/vsda.js
[11:53:36] [172.30.32.2][2a551e65][ManagementConnection] New connection established.
[11:53:36] [172.30.32.2][79e479d0][ExtensionHostConnection] New connection established.
[11:53:37] [172.30.32.2][79e479d0][ExtensionHostConnection] <533> Launched Extension Host Process.
File not found: /usr/local/lib/code-server/lib/vscode/extensions/keesschollaart.vscode-home-assistant-1.39.0/jinja-language-configuration.json
[11:57:30] [172.30.32.2][2a551e65][ManagementConnection] The client has disconnected gracefully, so the connection will be disposed.
[11:57:30] [172.30.32.2][79e479d0][ExtensionHostConnection] <533> Extension Host Process exited with code: 0, signal: null.

Screenshot showing CPU and Memory usage, where it starts increasing just before 12pm is when I started the addon, and where it drops is when I stopped the addon.

For context this is an Intel i7-6700T system (4 cores, 8 threads) with 8GB RAM.

I also experience the same problem. By opening VSCode, the CPU load of the addon goes to 95% + percent, to the point Home Assistant almost freezes. Using Raspberry Pi 4b 8 GB ram

Yes, this issue is affecting me as well. VSCode seems to leak memory and eventually starts to put demands on the swap file which increases CPU load making the system slowly less unresponsive. It took about a week before overwhelmed my NUC system (4GB of RAM and 1 GB Swap). A simple restart on the VScode extension cleared the problem.

I do have the same issue. RPi5 8Gb at 90% CPU and 80% ram usage just for this AddOn. Very sad as I like the funktionality

Same issue as #565 that has been an issue for some since Jan 2023, mine started about 4 months ago. Have to keep it disabled or Pi will overhear and shutdown

Same here, the only workaround is to start the addon, do the changes and then stop it again. Any alternatives out there?

Hi, just found this reddit thread, where there seems to be a solution. I did not try it in any way, just posting it to inform you. https://www.reddit.com/r/homeassistant/comments/1amue9p/vscode_addon_burning_the_cpu_even_when_closed/

I tried that fix previously and it did not work for me, I tried again just to be sure. This led me to see what I could figure out. Go see my post in the issue thread #https://github.com/hassio-addons/addon-vscode/issues/565#issuecomment-1937079817

This 100% fixed the problem for me, but creates it's own with the loss of features.

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!