[Detector Support]: Periodic Stuck Detection on AMD iGPU #19853
-
Describe the problem you are havingI’m running a TrueNAS-SCALE-24.10.2.4 server with an AMD Ryzen 7 PRO 8845HS and integrated Radeon 780M Graphics. Object detection is set up using the Every so often, I encounter the message: Version0.16.0-c2f8de9 Frigate config fileversion: 0.16-0
mqtt:
enabled: false
auth:
failed_login_rate_limit: 1/second;5/minute;20/hour
trusted_proxies:
- 172.16.0.0/12
detectors:
onnx:
type: onnx
model:
model_type: yolo-generic
width: 320
height: 320
input_tensor: nchw
input_dtype: float
path: /config/model_cache/yolov9-s.onnx
labelmap_path: /labelmap/coco-80.txt
ffmpeg:
hwaccel_args: preset-vaapi
go2rtc:
streams:
front_hikvision:
- ffmpeg:rtsp://[user]:[password]@[ip_addr]:554/Streaming/Channels/101
detect:
enabled: true
record:
enabled: true
retain:
days: 14
mode: motion
alerts:
retain:
days: 30
mode: active_objects
detections:
retain:
days: 30
mode: active_objects
objects:
track:
- person
- car
snapshots:
enabled: true
retain:
default: 7
birdseye:
enabled: true
mode: motion
width: 1280
height: 720
cameras:
front_hikvision:
enabled: true
ffmpeg:
inputs:
- path: rtsp://127.0.0.1:8554/front_hikvision
roles:
- detect
- record
output_args:
record: preset-record-generic
detect:
width: 1920
height: 1080
camera_groups:
[My]Home:
order: 1
icon: LuHouse
cameras: birdseye
notifications:
enabled: true
email: [user]@gmail.comdocker-compose file or Docker CLI command$ cat /mnt/.ix-apps/app_configs/frigate/versions/1.2.14/templates/rendered/docker-compose.yaml | jq
{
"services": {
"frigate": {
"cap_add": [
"CHOWN",
"DAC_OVERRIDE",
"FOWNER",
"KILL",
"PERFMON",
"SETGID",
"SETUID"
],
"cap_drop": [
"ALL"
],
"deploy": {
"resources": {
"limits": {
"cpus": "2",
"memory": "4096M"
}
}
},
"devices": [
"/dev/dri:/dev/dri",
"/dev/kfd:/dev/kfd"
],
"environment": {
"HSA_OVERRIDE_GFX_VERSION": "11.0.0",
"NVIDIA_VISIBLE_DEVICES": "void",
"TZ": "America/Port_of_Spain",
"UMASK": "002",
"UMASK_SET": "002"
},
"group_add": [
44,
107,
568
],
"healthcheck": {
"interval": "30s",
"retries": 5,
"start_interval": "2s",
"start_period": "15s",
"test": "curl --request GET --silent --output /dev/null --show-error --fail http://127.0.0.1:5000/api",
"timeout": "5s"
},
"image": "ghcr.io/blakeblackshear/frigate:0.16.0-rocm",
"platform": "linux/amd64",
"ports": [
{
"mode": "ingress",
"protocol": "tcp",
"published": 30193,
"target": 8971
},
{
"mode": "ingress",
"protocol": "tcp",
"published": 8554,
"target": 8554
},
{
"mode": "ingress",
"protocol": "tcp",
"published": 8555,
"target": 8555
},
{
"mode": "ingress",
"protocol": "udp",
"published": 8555,
"target": 8555
}
],
"privileged": false,
"restart": "unless-stopped",
"security_opt": [
"no-new-privileges=true"
],
"shm_size": "512M",
"stdin_open": false,
"tmpfs": [
"/tmp/cache:size=1073741824"
],
"tty": false,
"user": "0:0",
"volumes": [
{
"bind": {
"create_host_path": false,
"propagation": "rprivate"
},
"read_only": false,
"source": "/mnt/SSDs/Applications/frigate/config",
"target": "/config",
"type": "bind"
},
{
"bind": {
"create_host_path": false,
"propagation": "rprivate"
},
"read_only": false,
"source": "/mnt/HDDs/Applications/frigate/media",
"target": "/media",
"type": "bind"
},
{
"read_only": false,
"target": "/tmp",
"type": "volume",
"volume": {
"nocopy": false
}
}
]
}
},
"volumes": {},
"x-notes": "# Frigate\n\n## Security\n\n### Container: [frigate]\n\n- Is running as root user\n- Is running as root group\n\nDefault credentials are printed in the logs\nduring the first run of the application.\n\n## Bug Reports and Feature Requests\n\nIf you find a bug in this app or have an idea for a new feature, please file an issue at\nhttps://github.com/truenas/apps\n\n",
"x-portals": [
{
"host": "0.0.0.0",
"name": "Web UI",
"path": "/",
"port": 30193,
"scheme": "https"
}
]
}Relevant Frigate log outputInstall methodTrueNAS Apps Market Object DetectorOther (ROCm) Screenshots of the Frigate UI's System metrics pages
Any other information that may be helpfulWhen I first set this up, I tried running the YOLOv9-m model. After leaving it overnight, the app became very sluggish, and I noticed extremely high GPU usage. The app didn’t crash, but the model was consuming excessive CPU/GPU resources until it became unresponsive. I stopped the container and switched to the YOLOv9-s model, and I haven’t seen that behavior since. Hardware Info: |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 4 replies
-
|
The periodic "Detection appears to be stuck. Restarting detection process..." message when using Frigate with an AMD iGPU and ONNX detector is a known behavior observed on AMD integrated graphics, especially when running ONNX models like YOLOv9-s(1)(2)(3). This can be triggered by the detector process hanging or failing to make progress, often due to compatibility or stability issues with the ROCm/ONNX stack on certain AMD hardware(2)(4)(3). Key points and suggestions:
If you continue seeing periodic stuck detection, this is likely due to incomplete support for your specific iGPU in the ROCm/ONNX stack. There is no official workaround in the documentation beyond the steps you've already taken(2)(4)(3). For further troubleshooting:
There are no documented configuration changes that guarantee a fix for this on AMD iGPUs at this time(2)(4)(3). 📚 Sources:
Have another question? Just tag @inkeep. |
Beta Was this translation helpful? Give feedback.
-
|
As an update, running verion 0.16.1-e664cb2 for the past week I've not seen this issue reoccur. I'm cautiously optimistic that the current version resolved the issue. Will continue monitoring. |
Beta Was this translation helpful? Give feedback.
-
|
If your AMD CPU have Ryzen AI, you should really try Openvino (CPU) (don't GPU/Auto) and optional use YoloNAS. |
Beta Was this translation helpful? Give feedback.
-
|
Does Frigate have support for using the NPU on AMD CPUs? I didn't read anywhere on the Object Detectors page that this was a supported configuration. |
Beta Was this translation helpful? Give feedback.
-
|
Frigate DOC in OpenVINO said "OpenVINO is supported on 6th Gen Intel platforms (Skylake) and newer. It will also run on AMD CPUs despite having no official support for it." |
Beta Was this translation helpful? Give feedback.
-
|
No, NPUs are currently not supported for AMD |
Beta Was this translation helpful? Give feedback.
-
|
Yep, thank you for information, but I'm just running OpenVINO CPU detector on AMD 7940HS. |
Beta Was this translation helpful? Give feedback.
As an update, running verion 0.16.1-e664cb2 for the past week I've not seen this issue reoccur. I'm cautiously optimistic that the current version resolved the issue. Will continue monitoring.