@NickM-27 commented on GitHub (Mar 29, 2024):
which model did you use that did?
@jdgiddings commented on GitHub (Mar 29, 2024):
I'm experiencing the exact same error on TrueNAS Scale w/ GTX 1060
@Jautze82 commented on GitHub (Feb 14, 2024):
looks like you are using CPU detectors which are highly discouraged. At the very least you should be using openvino instead https://docs.frigate.v…
@usafle commented on GitHub (Mar 29, 2024):
@hvardhan20 and @jdgiddings - I hope you both get a response but, if my past experience holds true, it doesn't look good. CPU detection worked fine. …
@NickM-27 commented on GitHub (Mar 29, 2024):
There are many tensorrt users so this seems to be a very isolated problem. Like I said before, seg faults are difficult to debug and without being…
@jdgiddings commented on GitHub (Mar 29, 2024):
here's the output from nvidia-smi on the host. I believe these are all supported versions
NVIDIA-SMI 535.54.03 Driver Version: 535.54.03 CUDA…
@jdgiddings commented on GitHub (Mar 29, 2024):
yolov7-320 does not throw the segfault
@thetravellor commented on GitHub (Feb 12, 2024):
I had this issue with 0.13 beta, so I downgraded to 0.12 and all works well, now that…
@usafle commented on GitHub (Feb 12, 2024):
Edited Post to remove the Frigtate Plus API key and RTSP password that was visible in the Docker CLI command.
@usafle commented on GitHub (Feb 14, 2024):
No one has ANY suggestions (besides buying a CORAL device) on how to get my Frigtate instance up and running??
@NickM-27 commented on GitHub (Feb 12, 2024):
Would be good to see a screenshot of the system page and logs after frigate has been running
@NickM-27 commented on GitHub (Feb 14, 2024):
seg faults are difficult because it is usually something related to the host or the hardware and there is no info about what is going wrong.
From…
@Jautze82 commented on GitHub (Feb 13, 2024):
The problem, at least for me, is that the Raspberry Pi hardware acceleration in Frigate 0.13 does not work properly, which can lead to a random set…
@usafle commented on GitHub (Feb 16, 2024):
memtest complete. 0 errors.
Next suggestion please?
@NickM-27 commented on GitHub (Feb 13, 2024):
looks like you are using CPU detectors which are highly discouraged. At the very least you should be using openvino instead https://docs.frigate.video…
@hvardhan20 commented on GitHub (Feb 29, 2024):
I have the same error. Need help I have…
@Jautze82 commented on GitHub (Feb 13, 2024):
looks like you are using CPU detectors which are highly discouraged. At the very least you should be using openvino instead https://docs.frigate.vid…
@Jautze82 commented on GitHub (Feb 11, 2024):
I'm experiencing the same thing, usually happens after ~24 hours of uptime for me. I've got 5 cameras, and 2-3 tend to "die out" Clicking into them…
@usafle commented on GitHub (Feb 11, 2024):
@mike2307 commented on GitHub (Feb 11, 2024):
Probably it would also be a good idea to display the configured ui.timezone at all locations in the web UI which deal with date/time specifications.