[Support]: FFMPEG memory leak with restreaming #11676
Unanswered
Samywamy10
asked this question in
General Support
Replies: 1 comment 5 replies
-
This is an issue that has been reported by proxmox users before. It was sometimes found to be an issue with the GPU driver used and other times found to be a problem with the kernel used. |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Describe the problem you are having
Every ~12 hours memory usage starts to dramatically climb which leads to my Frigate container running out of memory, which leads to CPU usage being pinned to 100% and Frigate dies.
The strange part is, despite errors in the logs, that object detection, recording and even HomeKit viewing all work fine.
Diving further into this issue, I can see that the FFMPEG process for my Reolink E1 Pro camera is what’s taking up all the memory.
I have restreaming set up for this camera for two reasons:
I also want to know if there is a better way to achieve (2) as I’m still making two connections to the camera. It doesn’t look like I can use one go2rtc stream as an input to another.
(Before anyone asks, the camera is in the bathroom to watch our cats, and the camera is very obvious. Home Assistant uses the PTZ to point it at the wall when it detects people in the bathroom)
Very high memory usage for FFMPEG:
Proxmox screenshot:
Version
0.13.2-6476F8A
Frigate config file
Relevant log output
FFprobe output from your camera
Frigate stats
Operating system
Proxmox
Install method
Docker Compose
Coral version
CPU (no coral)
Network connection
Wired
Camera make and model
Reolink E1 Pro
Any other information that may be helpful
No response
Beta Was this translation helpful? Give feedback.
All reactions