@pipip commented on GitHub (Jan 28, 2024):
I have had something similar this night. Frigate has been running stable for days since last restart and suddenly RAM increases constantly: ![Screenshot…
@github-actions[bot] commented on GitHub (Feb 28, 2024):
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.…
@martinj9320 commented on GitHub (Jan 4, 2024):
Yes, this might be the easiest way to fix at least the symptoms for now. Thank you for your time and help. I'll leave this issue open, just in…
@NickM-27 commented on GitHub (Jan 3, 2024):
And how much RAM was being used at that time?
@martinj9320 commented on GitHub (Jan 3, 2024):
About 7,5 GB total, 5,2 GB in cache.
@NickM-27 commented on GitHub (Jan 3, 2024):
Without anything showing that it's using the cache it's difficult to offer a suggestion other than set a docker limit on the memory usage
@martinj9320 commented on GitHub (Jan 3, 2024):
Output of df - h /tmp/cache and du -h /tmp/cache inside the Docker container:
@martinj9320 commented on GitHub (Jan 3, 2024):
/tmp/cache doesn't exist.
Output of du -h /tmp:
@NickM-27 commented on GitHub (Jan 2, 2024):
it is very unlikely to be recordings, since frigate manages those and there would be errors in the logs.
You could check df -h /tmp/cache and…
@martinj9320 commented on GitHub (Jan 2, 2024):
Alright, I'll have to check this tomorrow as I'm currently off-site. Thank you so far.
@NickM-27 commented on GitHub (Jan 2, 2024):
need to figure out what is actually using the memory, your top screenshot shows the highest process only using 4% memory so it's not clear where the…
@martinj9320 commented on GitHub (Jan 2, 2024):
That's the problem, I have no idea how to figure this out. As you said, there is no process that is using an unreasonable amount of memory. As I'm…
@martinj9320 commented on GitHub (Jan 2, 2024):
I am already seeing the exact same behaviour as before, memory usage went from about 2 GB to almost 6 GB over the past hours, about 4 GB are…
@martinj9320 commented on GitHub (Jan 2, 2024):
Upgrading to v0.13 worked without any issues. I will report back in a week if this has solved the issue.
@martinj9320 commented on GitHub (Jan 1, 2024):
I will give it a try then. Thank you.
go2rtc supports variable substitution
@NickM-27 commented on GitHub (Mar 20, 2024):
This is covered in the docs at https://docs.frigate.video/configuration/#environment-variable-substitution
@martinj9320 commented on GitHub (Jan 1, 2024):
With which version of go2rtc does Frigate 0.13 come? Because for hardware transpose I'd still need to run v1.3.1 or higher.
@NickM-27 commented on GitHub (Jan 1, 2024):
LED control is not part of the onvif standard
@NickM-27 commented on GitHub (Jan 1, 2024):
You may want to update to the latest go2rtc or remove the custom go2rtc and upgrade to frigate 0.13 (currently in rc) which has a lot of improvements…