Checklist:
Home Assistant release with the issue:
0.101.3
UI (States or Lovelace UI?):
Lovelace UI
Browser and Operating System:
Safari 13.0.3
MacOS 10.15.1
Description of problem:
I pinned home assistant to the browser and check it regularly. Over time, the web site is consuming a lot of memory until Safari issues a warning:
"This webpage is using significant memory. Closing it may improve the responsiveness of your Mac"
In my case, activity monitor showed 1.5GB of memory usage for only the home assistant website.
Steps to reproduce this problem:
Pin a Home assistant tab to the browser and leave it open for a long time.
Are you using any custom lovelace cards?
I'm not sure what a custom card is. I just defined tabs for each room (8 in total). Just looked up custom cards - I use none of them.
Do you use camera streams?
No camera streams. Just sensors, a media player, weather and some switches.
Here is a screenshot of Safari with the memory timeline enabled. Each red mark indicates a manual "refresh". Max memory consumption is at 1.6GB. It seems that memory is sometimes not released for extended periods of time...

Same here.
@cmer also on safari?
Yes
I am seeing the same issue with a pretty lightweight setup (Philips Hue, Sonos, two Tasmota smart plugs), a simple reload of the main page shows 1 Gb of memory usage, most of which blames to "Page":

Looking at the Safari web inspector docs, it says:
Page – All other memory. This includes engine memory related to the DOM, styles, rendering data, memory caches, system allocations, etc.
Have that all the time, and have seen that for a very long time independent of the HA versions..Somehow have started to learn to live with it...
Never saw that in safari inspector though, might give a clue to debug the issue. How do you show this memory use in Inspector?
You need to enable the developer menu in Safari, then go to the Timelines tab, click the "Modify" button to select the Memory tool, then reload the page. This is what the whole thing looks like for me (sorry for the French UI):

Since the memory used is all in the "Other" bucket (so not JavaScript or images) I don't really know how to drill further, maybe walk through the DOM and look for absurdly deep element hierarchies?
how odd, I don't have the memory in the left side tools

See: https://stackoverflow.com/questions/48465464/cant-see-safari-developer-timelines-memory-instrument
Am 04.01.2020 um 12:30 schrieb Marius notifications@github.com:
how odd, I don't have the memory in the left side tools—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
thanks! couldn't select the checkbox though, and couldn't scroll the options. Was only able to slide the full inspector up which revealed the left side options, of which memory is 1.
Will report when I see the excessive power usage notification
Same problem here, quite long time (1 year?). Worst place is in /states in Developer Tools. I get the usual "This web page is using significant memory", page is unresponsive and my laptop is hot as hell.
States is expected especially with a lot of states. It should be virtualized, that will solve it probably.
History and Logbook are critical places too, with around 1200 statuses (I think this is not as much) it takes 65sec to load, @2GB RAM and same issue.
Same issue with a minimal setup that I just built. Just two lights and a handful of sensors.
The usage goes up especially when I configure the UI.
I have the same issue. After some time the memory goes upp to 40%. When I reboot the memory goes down to 15 %. Something is leaking. Running 0.109.6
@jazbraz that is your server memory or your client memory?
I really don´t know? It is my "sensor.memory_use_percent" in home assistant.
That would be your server, this issue is about the client (browser).
ok sorry
That would be your server, this issue is about the client (browser).
ok sorry.
Fixed this with answer from a duplicate issue. I simply had to turn off content blockers for my HA server. Everything’s good now.
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Most helpful comment
https://github.com/home-assistant/home-assistant-polymer/pull/4450