LTSS takes down HA because of memory leak

[michalk-k]

The problem

I've been advised to inform the Core maintainers that ltss custom component can cause HA instability due to memory leak. In my setup it fills the whole memory (8GB) in two days, causing HA to restart. With this component excluded, the setup is rock-stable - I tested it multiple times.

Since I'm a new user of ltss I cannot say since which version the ltss has this flaw.

The error the ltss failed on, might be possibly interesting for the HA core owners too. I've filed the issue to ltss repository: https://github.com/freol35241/ltss/issues/213

What version of Home Assistant Core has the issue?

core-2024.8.3

What was the last working version of Home Assistant Core?

N/A

What type of installation are you running?

Home Assistant OS

Integration causing the issue

LTSS

Link to integration documentation on our website

https://github.com/freol35241/ltss

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[cryptk]

Just a heads up that I am also experiencing a pretty bad memory leak and I am NOT using the LTSS custom component. I'm not done with my own troubleshooting yet, but I have confirmed that the memory leak occurs even when running Home Assistant in safe mode (no custom integrations).

[joostlek]

• Start a new issue, choose profiler as the integration

• Include a callgrind file from the https://www.home-assistant.io/integrations/profiler/ profiler.start service

• If memory is leaking, include 4 hours of RAW logs (Settings -> System -> Logs -> Download) from the https://www.home-assistant.io/integrations/profiler/ profiler.start_log_objects service with the default settings

[issue-triage-workflows[bot]]

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 has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[michalk-k]

So while the problem causing ltss to stop (and in turn leaking memory) has been fixed, the memory leak seems to be not fixed.

Recently TimescaleDB stopped responding, which again rendered in increasing usage of memory.

So, there is serious suspicion that LTSS starts eating memory in an uncontrolled manner after losing the ability to store data in TimescaleDB.

Even worse, after reconnecting to TimescaleDB, it doesn't release the memory.

[issue-triage-workflows[bot]]

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 has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[issue-triage-workflows[bot]]

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 has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.