core: ring integration - hass process quickly takes all available memory and OOMs.
The problem
With the new built-in ring integration (i.e. not using ring: in configuration.yaml), hass continues to grow in memory size rapidly, using all available memory. This continues until the OOM reaper comes along and kills hass. I have a 1G system and it takes approx 48 hours before hass OOMs. Disabling the new ring integration returns hass to stable memory usage, taking no more than 15% of my memory.
Environment
Home Assistant 0.104.3 Path to configuration.yaml: /home/ha/.homeassistant
- Home Assistant release with the issue: 0.104.3
- Last working Home Assistant release (if known): 0.103
- Operating environment (Hass.io/Docker/Windows/etc.): Native Debian Linux x64 Install, virtualenv
- Integration causing this issue: ring
- Link to integration documentation on our website: https://www.home-assistant.io/integrations/ring/
Problem-relevant configuration.yaml
There is no yaml configuration - it uses the native integration now.
Traceback/Error logs
There are no obvious errors, just memory size of the hass process increasing and increasing.
Additional information
I have two Ring products - A Ring Doorbell 2 and a Ring Floodlight. I am using 2FA on my ring account. I have been using the ring integration perfectly for the last ~year, it is only since moving to the built-in integration that the memory leak has started.
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 21 (5 by maintainers)
jemalloc is the default in our container nowadays.