-
-
Notifications
You must be signed in to change notification settings - Fork 31k
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
2024.10 - 2024.11.4 - Memory Leak [Docker Version] #131531
Comments
Please run all your tests in safe mode. Also please provide the logs from safe mode. |
How fast does it fill up? |
Its about 100MB/h filling the RAM. I Updated the initzial Post with a callgrind file for 30seconds standard setting in safe mode also the full log in safe mode. Its not 4 hours but i guess the problem is the same. Should i add some of the logs after a few more hours? |
I have to check the callgrind, but I'm not behind my pc for the following few days. But to confirm, you made it in safe mode right? |
Yes its in safe mode since 2 hours now. Thanks for helping :) no problem, enjoy beeing away from a computer for a few days. |
The problem
Since the Update to 2024.10.3 or .4 there is a memory leak that is killing the container via the oom killer and then restarting.
What version of Home Assistant Core has the issue?
core-2024.11.4
What was the last working version of Home Assistant Core?
2024.10.1
What type of installation are you running?
Home Assistant Container
Integration causing the issue
core
Link to integration documentation on our website
No response
Diagnostics information
home-assistant_2024-11-25T12-56-02.695Z.log
callgrind.out.zip
will update when profiler is done.
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
I tried in safe mode, it also ate memory no difference.
The text was updated successfully, but these errors were encountered: