High memory consumption

[MikeBP13]

Problem/Motivation

Every time I open the add-on, the memory consumption increases significantly (>3% on a 16GB installation) even without doing anything with it...

Expected behavior

Keep memory consumption low if add-on doesn't perform any actions - similar to the behavior experienced several months ago (at least 2-3 releases ago)

Actual behavior

See reason

Steps to reproduce

1. Restart the add-on -> memory consumption is low
2. Open the add-on -> huge jump in memory consumption without doing anything (no files are open, ...)

Proposed changes

No idea...

[davidrapan]

Yeah and at least as far I know it started happening w/ some of the recent updates... but I noticed that it is already mentioned in several other issues. 😉

[sp0ngeboobs]

also the same problem. It took 4GB of RAM. Rebooting HA does not work, you need to reboot the entire addon to clear the memory. Every day takes away a little bit of memory

[MikeBP13]

also the same problem. It took 4GB of RAM. Rebooting HA does not work, you need to reboot the entire addon to clear the memory. Every day takes away a little bit of memory

I can confirm: HA restart does not help. You need to restart the add-on or reboot the machine hosting HA to clear the memory. Even after restart, the consumed memory slowly increases each day even though the add-on is not used.

[LogicAnalysis]

I also had the same issue. As @sp0ngeboobs said, restarting HA doesn't solve the issue. Restarting the addon does provide a temporary remedy. In my case, it was using >10gb of RAM! I only noticed when Frigate failed to start due to signal 9, and I had to investigate. Turns out VS was hogging all the RAM

[sca075]

Had noticed the same, and I guess there was a similar issue in the past. I would say CPU and Memory rump up and I can confirm that restarting the addon is the only option as per I guess HA is restarting only itself. I just roll back the addon to the the earlier release as the last was publish in November there was still a backup available. If this somehow solve the problem will let you know.

[sca075]

5.17.3 is currently reinstalled and CPU is stable at 1.5% 0.95%.. memory is fix at 0

[matthewcbyington]

I'm on 5.18.0 and still seeing high memory consumption.

[conducton]

To solve temporary the issue I added an automation to restart the add-on when it reached 8 clients.
Not the best solution but it's working.

Here is the code :
alias: Restart_VSCODE
description: ''
triggers:

• trigger: numeric_state
  entity_id:
  • sensor.connected_clients
    above: 8
    conditions: []
    actions:
• action: hassio.addon_restart
  data:
  addon: a0d7b954_vscode
  mode: single

to add the sensor.connected_clients i followed https://www.home-assistant.io/integrations/websocket_api/

[glemag]

Confirming the same, version 5.18.1., memory usage from 4Gb about 15%

[MikeBP13]

It's getting worse: editing 4 files from config directory, the addon used memory reached 25% of 16GB...

[glemag]

Also confirming that it's happened since last versions...

[kwkid]

Glad I found this thread. The same is happening to me but only when I am using a Chrome browser. Switching to Microsoft Edge I do not experience the high memory usage or constant freezing of vs code. Perhaps someone can confirm this.

[ZipingL]

Yeah this happens to me (it did not happen before in the past).

• This seems to occur after using this addon after a few minutes of usage.
• The memory consumption and cpu consomption then become unreasonably high, I'm talking about it using 99% of the CPU, but for me memory is not that big of a concern, but is also high.

I'm guessing this is not supposed to occur.

[github-actions]

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!