[Support]: Problems with RAM usage #19743
Replies: 1 comment
-
There is no documentation detailing a general RAM leak or memory climb specific to Frigate 0.16.0. However, the documentation highlights some important aspects to check for RAM usage:
You can calculate the recommended shm size for your setup using the formula in the docs:
For multiple cameras, multiply the result by the number of cameras and add extra for logs(1). If you continue to see memory growth, monitor /dev/shm usage and system metrics, and ensure all camera streams are stable and reachable. For further troubleshooting, you may want to review the installation guide and hardware acceleration docs. 📚 Sources: Have another question? Just tag @inkeep. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the problem you are having
Hi

Since I updated to frigate 16 I noticed some strange behavior. My Ram usage goes up and up - you can see it in the picture. You can see the point where I restarted frigate, and in the End you can see the point where I stopped the addon completely. After that the Ram usage keeps normal.
The Version before didn't have those problems. Three cameras are only active when alarmo is active - so its normal that they are not found
Version
0.16.0
What browser(s) are you using?
No response
Frigate config file
Relevant Frigate log output
Relevant go2rtc log output
FFprobe output from your camera
Frigate stats
No response
Install method
Home Assistant Add-on
docker-compose file or Docker CLI command
Object Detector
Coral
Network connection
Wired
Camera make and model
divers Reolink
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