@NickM-27 commented on GitHub (Mar 22, 2024):
That seems abnormal. I have 8 cameras running 1280x720 or similar and frigate never uses more than 3GB of RAM
@heisenberg2980 commented on GitHub (Mar 22, 2024):
@NickM-27 that used to be the case for me with v0.12 but when I upgraded to v0.13 the amount of memory used increased a lot, usig the same…
@NickM-27 commented on GitHub (Mar 22, 2024):
That is probably right, peewee keeps parts of the database cached in memory. In the next version of Frigate there is a possibility the thumbnails…
@heisenberg2980 commented on GitHub (Mar 22, 2024):
That would be amazing as it would reduce the size of the database a lot
@transplier commented on GitHub (Mar 23, 2024):
@transplier running Frigate with 2Gb of RAM is a real miracle (even with 4Gb is a miracle for me), how many cameras and what resolution do your…
@github-actions[bot] commented on GitHub (Apr 23, 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.…
@heisenberg2980 commented on GitHub (May 6, 2024):
For anyone coming here with this issue running Frigate in a proxmox LXC, the reason for the issue has been found here: https://github.com/blakebl…
@heisenberg2980 commented on GitHub (Mar 22, 2024):
@transplier running Frigate with 2Gb of RAM is a real miracle (even with 4Gb is a miracle for me), how many cameras and what resolution do your…
@transplier commented on GitHub (Mar 22, 2024):
I'm also seeing much increased memory usage since upgrading around Feb. 17th. A bit hard to interpret these graphs but it perhaps looks like more…
@d3relict commented on GitHub (Mar 1, 2024):
allowing 3GB memory for the container seemed to have fixed my issue. however, the change in memory usage from 0.12 to 0.13 is quite dramatic: ![image]…
@remz1337 commented on GitHub (Feb 28, 2024):
I have upgrade my whole install yesterday and logs seem clean since then. Will keep you updated. Here's what I have upgraded (in order):
1.…
@Strux-DK commented on GitHub (Jan 21, 2024):
@GobbleTurkey unfortunately that did not work for me
@NickM-27 commented on GitHub (Jan 19, 2024):
@remz1337 that log won't be causing this memory issue, it is saying a single object was memory leaked only. If you are not already then I'd suggest…
@Answer-1 commented on GitHub (Jan 20, 2024):
So far so good, not memory issues nor docker restarts when not using the restream for Frigate. I also did some other tests and can affirm that most…
@cgils commented on GitHub (Jan 29, 2024):
@Strux-DK: The model filename is "coco nine one c l" (the letter L), not "coco nine one c one".
@github-actions[bot] commented on GitHub (Feb 20, 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.…
@github-actions[bot] commented on GitHub (Feb 29, 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.…
@Jbithell commented on GitHub (Jul 14, 2024):
I've been getting the same issue as the above - @Strux-DK @cgils did you ever get to the bottom of what this error means?
@heisenberg2980 commented on GitHub (Feb 20, 2024):
Having the same issue, and it started just after I upgraded Frigate to v0.13 (I upgraded it on 3rd Feb and the issues started the same day).…
@d3relict commented on GitHub (Feb 28, 2024):
started receiving this error after upgrading to 0.13.2 (0.12.x worked fine). the only thing i can see in frigate logs are as follows (unrelated nginx…