Apparent memory leak

[ScottG489]

Problem/Motivation

This addon increases in memory consumption until my system runs out.

I've been monitoring it since my last incident and I had to restart the host. The host has a total of 4GB of memory which meets the documented requirements.

Though I've only been tracking memory per-addon for the duration of the first graph, I have been running this addon for over a year and I've only been having memory usage issues recently:

I usually update addons pretty quickly after there's a release, and I can see v5.4.1 was released right around that time. Though from the release notes nothing sticks out.

I'm on the latest version and default config.

Expected behavior

For the memory usage of this addon to not increase indefinitely.

Actual behavior

Memory appears to increase indefinitely. Last time my system used up all memory and swap and locked up due to swap disk usage and I had to restart.

Steps to reproduce

As far as I can tell I'm using VS Code normally. I've only installed one extension (vim).

Unfortunately, I don't have any more information than above, but I'm happy to troubleshoot and get more information if you have suggestions on how to do so. I connected to the container and it doesn't have ps or even free so it seems like my tooling in the container is limited.

Thoughts on what this could be?

[leowinterde]

Same problem here.

[limitless00net]

Same problem here.

[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!

[JonathanVarild]

Just updated my Home Assistant addons and started experiencing issues with my home "lagging". After investigating the issue, I noticed that the Visual Studio addon consumed 95% CPU and 57% ram. Turning the addon off lowered the overall resource usage on my Home Assistant system. See attached pictures.

[ScottG489]

Still an issue.

[doug-hoffman]

I've also seen a memory leak...

I noticed that it started happening after I opened folder /, because I was going back and forth between editing a local addon and HA config. After switching back to /config and restarting vscode, I haven't seen the problem again.

[BNolet]

I specifically started configuring the Terminal & SSH addon to be able to use VSCode Remote - SSH specifically because of this memory issue.

My theory is that with each loading of the VSCode web interface, it's spinning up a new process without killing the old one. I say this because judging by the memory footprint over time, I can see stark stepwise jumps of memory use.

[ScottG489]

@BNolet I've seen similar spike patterns as well and had also theorized that. I wonder if something changed recently with how new instances are being spun up.

I'm also considering using an external client, though I'll be using intellij instead. I've already got it working via sshfs.

[VNRARA]

Have any of you guys been experiencing random reboots because of this maybe? My HA install has been rebooting pretty frequently and couldn't find a culprit. I've started disabling add-ons and after I noticed (see #589 as well) VSS uses port 1337 which shows up a lot in the logs.

[ScottG489]

@VNRARA I've had to manually reboot my system because I ran out of memory, and soon after swap. Once everything starts swapping to disk the system essentially locks up.

I'd suggest enabling resource usage sensors for your add-ons. I've found it very valuable since I've done so. You can do this by going to the services created for each add-on and enabling the CPU and memory percent sensors.

[VNRARA]

I think both Node-Red and VSCode might be culprits here. (I'm on a 4GB system)

VS code is already using: +100mb RAM from boot and Node-Red +115MB.

This also sometimes happens:

[02:28:34] [172.30.32.2][c05a3361][ManagementConnection] Unknown reconnection token (never seen).
[02:28:34] [172.30.32.2][e68f3661][ExtensionHostConnection] Unknown reconnection token (never seen).
[02:34:01] [172.30.32.2][e9f8b661][ManagementConnection] New connection established.
[02:34:03] [172.30.32.2][aa78680f][ExtensionHostConnection] New connection established.
[02:34:03] [172.30.32.2][aa78680f][ExtensionHostConnection] <468> Launched Extension Host Process.

[ScottG489]

I think a few hundred MB for either of those is more than acceptable.

Bringing this discussion back on topic though, I'd pay attention to sustained increases to the memory usage of VS Code as an indicator that you're also seeing a memory leak.

[Xlinx64]

I have the same issue on my home assistant blue, after I disabled VSCode and didn’t use it anymore I didn’t have any reboots. When I used it heavily it crashed every half an hour.

[VNRARA]

Mine did crash so it may also be node-red

[ScottG489]

@Xlinx64 Wow that's pretty bad if it happens so quickly. I'd double check the system requirements in the docs for this add-on to make sure your system meets them.

Also, here's an automation I created as a fallback to restart the add-on if it uses up too much memory. Be sure to change the value based on your system's resources:

trigger:
  - platform: numeric_state
    entity_id: sensor.studio_code_server_memory_percent
    above: 20
action:
  - service: hassio.addon_restart
    data:
      addon: a0d7b954_vscode

[Xlinx64]

@ScottG489 Thank you for the script!
But I dont dare to use the add-on until it is fixed. I use the File Editor add-on for now.
I have to admit that on the day with the crashes I opened and closed it a lot since I did some template sensors.

[BNolet]

You can also use VSCode Remote - SSH with the SSH & Terminal add-on if you're looking for a longer term solution: https://community.home-assistant.io/t/vs-code-remote/129887/24?u=brandonnolet

[boojew]

Yea, I have the same issue on 16gb machine.. Takes about 1-2 weeks before I run out of memory :( Could be related to coder/code-server#5201, but that is super vague.

[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!

[ScottG489]

Still an issue.

[MiddleSiggy]

I am having the same issue, I posted some more information in this ticket:
coder/code-server#6213

[rbalaev]

the same problem, until the complete loss of memory

[le-clu]

Same issue here.
I keep VSCode off, and only switch it one when needed. Today I forgot to switch it off again and had to hard-reboot my Pi.

[ScottG489]

If you'd like to help manage this for now, you can create an automation to restart the VSCode add-on if it uses up too much memory. Something like this (adjust the above number for your situation):

trigger:
  - platform: numeric_state
    entity_id: sensor.studio_code_server_memory_percent
    above: 20
action:
  - service: hassio.addon_restart
    data:
      addon: a0d7b954_vscode

Note that you'll need to enable the memory entity for this add-on in the supervisor integration.

[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!

[ScottG489]

Still an issue.

[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!

[Maddjik]

Still an issue for me

…

On Mon, Jul 8, 2024, 4:18 a.m. github-actions[bot] ***@***.***> wrote: 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! — Reply to this email directly, view it on GitHub <#565 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BEA34FTA3SUHZ46HW7XAOI3ZLJDNFAVCNFSM6AAAAAATYXSYEKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJTGMZTIOJWGQ> . You are receiving this because you commented.Message ID: ***@***.***>

[mniewiera]

sadly the same for me. have to restart the addon everytime i use it.

[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!

[ScottG489]

Still an issue.

[xamboozi]

I'm experiencing this as well

[sinclairpaul]

As it's an IDE, I'm confused by all the comments as to why you can't just stop the addon when not in use. I don't believe that the source application is designed to perpetually run.

[Maddjik]

As it's an IDE, I'm confused by all the comments as to why you can't just stop the addon when not in use. I don't believe that the source application is designed to perpetually run.

The resource hogging happens in the first few minutes I launch the program. After 5-10 minutes, if I don't stop it my HAOS VM becomes unstable and I gotta force restart it via the hypervisor. It is literally not usable.

[Ftown14]

That is the problem, and you have to. It doesn't change the fact that there is a memory leak. That is why it is submitted as an issue.

[sinclairpaul]

The resource hogging happens in the first few minutes I launch the program. After 5-10 minutes, if I don't stop it my HAOS VM becomes unstable and I gotta force restart it via the hypervisor. It is literally not usable.

Then it isn't the same issue as originally logged (which was an increase in memory usage over time). I would suggest looking at how you have the app configured (i.e. which folders it is running fil watchers for), and also resources on your system.

[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!

[le-clu]

This is still an issue.

[koyukan]

Problem still persist as of October 3, 2024

Home Assistant Supervised
Raspberry PI 4

1.2 GB Memory Usage after opening and closing 3 VSCode tabs.

[DjordjeMandic]

October 15, 2024
Everything updated to latest version
Still persists

[exec182]

I have the same Issue and found a bit more Information.
The Extension in VSCode "Home Assistant Config Helper" has this much load and memory usage. When i disable this extension and restart the Add-on is the Load in normal limits.

EDIT:
When i set manual the Connection for the Add-On in VSCode with a new generated Long Lived Access Token is the Issue also done.

[Dillton]

Hi.
I am joining this issue as I just by coincidence discovered my StudioCode add-on is using 107% RAM.
I am running on Intel NUC with Proxmox and HAOS in VM assigned 8GB RAM.

I did add-on restart and it's back in normal but question is for how long.

[ViezeVisNL]

Great to see we are going to reach a 2 year anniversary on this issue.

[vgdh]

I've stumbled on this problem with my instance.

[Dillton]

6 hours later it's growing again.

I don't know if this is wrong but I see it's started to complaining about some missing files.

[doula78]

Same issue on Studio Code Server 5.17.2 :

[pressurejets]

Same issue on Studio Code Server 5.17.3