[Support]: High memory consumption, detections stop after 24 hours #15133
Unanswered
nkfs
asked this question in
General Support
Replies: 1 comment 3 replies
-
it would be good to understand specifically what process is being killed for OOM |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Checklist
Describe the problem you are having
I am running frigate 0.14.1-f4f3cfa using docker on a linux server. The server has 32GB of RAM (approx 20GB available to frigate), with an attached USB Coral and Nvidia GPU. It is hosting 12 1080p cameras via go2rtc restream; 6 cameras are running detect/record, the other 6 are just for live view (no record / detect). Everything works as expected when the container is started, but over the course of 24 hours, it consumes all available ram causing the OOM killer to terminate ffmpeg processes. Then errors about the coral show up ([Coral is very slow (173224939361.34 ms)])j, and detection no longer works until I restart the container. The rest of frigate seems to work as expected, my live streams still display, and connection to home assistant is still fine.
Steps to reproduce
1.Start container
2.Wait approximately 24 hours
3.Detections stop occuring
...
Version
0.14.1-f4f3cfa
In which browser(s) are you experiencing the issue with?
Chrome Version 130.0.6723.69 (Official Build) (64-bit)
Frigate config file
docker-compose file or Docker CLI command
Relevant Frigate log output
Relevant go2rtc log output
No relevant erros in go2rtc
Operating system
Other Linux
Install method
Docker Compose
Network connection
Wired
Camera make and model
Mix of hikvision, unifi g3 (non protect), and generic rtsp
Screenshots of the Frigate UI's System metrics pages
Any other information that may be helpful
No response
Beta Was this translation helpful? Give feedback.
All reactions