-
-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
High memory consumption #905
Comments
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. 😉 |
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. |
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 |
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. |
5.17.3 is currently reinstalled and CPU is stable at 1.5% 0.95%.. memory is fix at 0 |
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
Proposed changes
No idea...
The text was updated successfully, but these errors were encountered: