@matew00 commented on GitHub (Sep 9, 2024):
Yes, issues on the host triggered by frigate 0.14. 0.13 worked in this way flawlessly. There are some who have the same version 6.12.10 along with…
@NickM-27 commented on GitHub (Sep 9, 2024):
Not sure how 0.14 would be the cause as the AMD GPU driver used is the same version as 0.13 as well as the same ffmpeg version.
You could try…
@matew00 commented on GitHub (Sep 11, 2024):
Thank you for your feedback, I will try few steps (including alter ffmpeg with a newer vesrion). In the meantime I have spin up a second frigate…
@johnmarksilly commented on GitHub (Sep 21, 2024):
So strange. I just stumbled upon this thread. I get an OS hang around once a month.
I am using a Dell Optiplex full form factor. Only thing…
@NickM-27 commented on GitHub (Sep 21, 2024):
That's fine for 0.14, 0.15 not as much is needed (could just be 1gb)
@PilaScat commented on GitHub (Sep 4, 2024):
it does work, I use this for a number of my containers.
working using --memory=8g --kernel-memory=8g
Should that work on…
@vista- commented on GitHub (Sep 9, 2024):
Update on my 0.14 setup on a Skylake Intel:
I managed to get it stable by setting the hwaccel to only use QSV instead of VAAPI. Been running for…
@ivanjx commented on GitHub (Sep 9, 2024):
@vista- your config crashes my i5-6500T a couple hours later.
i915 0000:00:02.0: [drm] GPU HANG: ecode 9:1:8ed97ff2, in frigate.detecto [942217]
@matew00 commented on GitHub (Sep 9, 2024):
Hello,
similar issue here. Introduced in 0.14. ffmpeg decoding using AMD iGPU, first the streams/cameras become unavailable, then the whole…
@NickM-27 commented on GitHub (Sep 9, 2024):
Without logs, dmesg, etc there's not much to go off of here. I have two Frigate instances running using my AMD 5700G iGPU without any issues.
@matew00 commented on GitHub (Sep 9, 2024):
Without logs, dmesg, etc there's not much to go off of here. I have two Frigate instances running using my AMD 5700G iGPU without any issues.
Here,…
@NickM-27 commented on GitHub (Sep 9, 2024):
Yeah, looks like issues on the host. Since yours is newer perhaps the older kernel that Unraid uses has issues, perhaps Unraid 7 with the newer kernel…
@djcrawleravp commented on GitHub (Sep 3, 2024):
is there a way to limit the ram for the container? so at least only it crashes and not the other 30 dockers otherwise I'll have to turn it…
@PilaScat commented on GitHub (Sep 3, 2024):
yes https://docs.docker.com/engine/containers/resource_constraints/
Other than this? It doesn't work For now I stopped the container, already 2…
@PilaScat commented on GitHub (Sep 3, 2024):
hwaccel_args: ' '
yes, but maybe is hardware related, I can say that with 0.14.1 crashes are more frequent than 0.14, don't know why
@NickM-27 commented on GitHub (Sep 3, 2024):
it does work, I use this for a number of my containers.
@PilaScat commented on GitHub (Sep 4, 2024):
it does work, I use this for a number of my containers.
working using --memory=8g --kernel-memory=8g
@djcrawleravp commented on GitHub (Sep 4, 2024):
it does work, I use this for a number of my containers.
working using --memory=8g --kernel-memory=8g
Should that work on raspberry…
@PilaScat commented on GitHub (Sep 3, 2024):
is there a way to limit the ram for the container? so at least only it crashes and not the other 30 dockers otherwise I'll have to turn it off until…
@NickM-27 commented on GitHub (Sep 3, 2024):
yes https://docs.docker.com/engine/containers/resource_constraints/