Please everyone:Why do I find that the usage rate of Detector CPU is very high after running the latest version of frigate, between 100% and 200%? Is this a normal situation? #16944

zhuzhuani · 2025-03-04T16:08:18Z

zhuzhuani
Mar 4, 2025

Here is my frigate configuration file

mqtt:
  host: 10.0.2.10
  user: something
  password: something
detectors:
  ov:
    type: openvino
    device: AUTO
    model_path: /openvino-model/ssdlite_mobilenet_v2.xml
model:
  width: 300
  height: 300
  input_tensor: nhwc
  input_pixel_format: bgr
  labelmap_path: /openvino-model/coco_91cl_bkgr.txt
ffmpeg:
  hwaccel_args: preset-vaapi
cameras:
  DoorWay_Camera:
    zones: 
      DoorWay: 
        coordinates: 2211,1620,756,1620,1719,531,2530,808
        objects: 
          - person 
    ffmpeg:
      output_args:
        record: preset-record-generic-audio-aac
      inputs:
        - path: rtsp://admin:test@xx.xx:554/h265/ch1/main/av_stream
          roles:
            - detect
            - audio
            - record
    detect:
      width: 2880
      height: 1620
      fps: 5
    onvif:
      host: x.x.x.x
      port: 80
      user: admin
      password: something
  Home_Camera:
    ffmpeg:
      output_args:
        record: preset-record-generic-audio-aac
      inputs:
        - path: rtsp://admin:test@yy.yy:554/h265/ch1/main/av_stream
          roles:
            - audio
            - record
  Pet_Camera:
    ffmpeg:
      output_args:
        record: preset-record-generic-audio-aac
      inputs:
        - path: rtsp://admin:test@zz.zz:554/h265/ch1/main/av_stream
          roles:
            - record
            - audio
audio:
  enabled: true
  min_volume: 500
  listen:
    - scream
    - speech
    - yell
  filters:
    speech:
      threshold: 0.8
snapshots:
  enabled: true
  required_zones: 
    - DoorWay
  retain:
    default: 30
record:
  enabled: true
  retain:
    days: 15
    mode: motion
  alerts:
    retain:
      days: 30
  detections:
    retain:
      days: 30
version: 0.15-1

The following is the Docker composed file:

services:
frigate:
image: ghcr.io/blakeblackshear/frigate:stable
stop_grace_period: 30s
container_name: frigate
privileged: true
Shm_Size: '1gb' 
restart: unless-stopped
network_mode: bridge
ports:
- "5000:5000"
- "8554:8554"
- "8555:8555"
- "8555:8555/udp"
volumes:
- /data/HDD4T/Media/frigate:/ media/frigate
- /data/HDD1T/docker/frigate/config:/ config
- /etc/localtime:/ etc/localtime:ro
devices:
- /dev/dri/renderD128:/ dev/dri/renderD128
environment:
- FRIGATE_RTSP_PASSWORD=793038260zZ
tmpfs:
-/tmp/cache: size=100000000

My configuration is CPU: 10100 GPU is the core display of CPU, i.e. UHD630

After searching for various solutions online, I tried a method to configure the frigate

detectors:
  ov:
    type: openvino
    device: AUTO
    model_path: /openvino-model/ssdlite_mobilenet_v2.xml
model:
  width: 300
  height: 300
  input_tensor: nhwc
  input_pixel_format: bgr
  labelmap_path: /openvino-model/coco_91cl_bkgr.txt

replace with：

detectors:
  ov:
    type: openvino
    device: GPU

model:
  width: 300
  height: 300
  input_tensor: nhwc
  input_pixel_format: bgr
  path: /openvino-model/ssdlite_mobilenet_v2.xml
  labelmap_path: /openvino-model/coco_91cl_bkgr.txt

##If configured in this way, the camera screen will turn black, the image will not be displayed, and a large number of errors will occur, as shown below:


Too many unprocessed recording segments in cache for Home_Camera. This likely indicates an issue with the detect stream, keeping the 6 most recent segments out of 7 and discarding the rest...
warning | 2025-03-04 23:54:47 | frigate.record.maintainer | Too many unprocessed recording segments in cache for Pet_Camera. This likely indicates an issue with the detect stream, keeping the 6 most recent segments out of 7 and discarding the rest...
warning | 2025-03-04 23:54:57 | frigate.record.maintainer | Too many unprocessed recording segments in cache for Home_Camera. This likely indicates an issue with the detect stream, keeping the 6 most recent segments out of 7 and discarding the rest...
warning | 2025-03-04 23:54:57 | frigate.record.maintainer | Too many unprocessed recording segments in cache for Pet_Camera. This likely indicates an issue with the detect stream, keeping the 6 most recent segments out of 7 and discarding the rest...
warning | 2025-03-04 23:55:07 | frigate.record.maintainer | Too many unprocessed recording segments in cache for Home_Camera. This likely indicates an issue with the detect stream, keeping the 6 most recent segments out of 7 and discarding the rest...
warning | 2025-03-04 23:55:07 | frigate.record.maintainer | Too many unprocessed recording segments in cache for Pet_Camera. This likely indicates an issue with the detect stream, keeping the 6 most recent segments out of 7 and discarding the rest...
info    | 2025-03-04 23:55:12 | watchdog.DoorWay_Camera   | FFmpeg did not exit. Force killing...
error   | 2025-03-04 23:55:12 | frigate.video             | DoorWay_Camera: Unable to read frames from ffmpeg process.
error   | 2025-03-04 23:55:12 | frigate.video             | DoorWay_Camera: Unable to read frames from ffmpeg process.
error   | 2025-03-04 23:55:12 | frigate.video             | DoorWay_Camera: Unable to read frames from ffmpeg process.

Requesting your assistance！

Answered by hawkeye217

Mar 4, 2025

See the FAQ, Upgrade Issues question 1.

View full answer

hawkeye217 · 2025-03-04T16:10:05Z

hawkeye217
Mar 4, 2025
Collaborator

We will need to see a full copy of the logs from Frigate startup.

4 replies

zhuzhuani Mar 4, 2025
Author

We will need to see a full copy of the logs from Frigate startup.

thanks!

When the content of the configuration file is the first situation I mentioned, the startup log occupies 100% to 200% as follows:

2025-03-05 00:37:55.592451363  [INFO] Preparing Frigate...
2025-03-05 00:37:55.696073131  [INFO] Starting Frigate...
2025-03-05 00:37:57.813786129  [2025-03-05 00:37:57] frigate.util.config            INFO    : Checking if frigate config needs migration...
2025-03-05 00:37:57.830609637  [2025-03-05 00:37:57] frigate.util.config            INFO    : frigate config does not need migration...
2025-03-05 00:38:00.900436953  [2025-03-05 00:38:00] frigate.app                    INFO    : Starting Frigate (0.15.0-cea210d)
2025-03-05 00:38:00.919103388  [2025-03-05 00:38:00] peewee_migrate.logs            INFO    : Starting migrations
2025-03-05 00:38:00.920348939  [2025-03-05 00:38:00] peewee_migrate.logs            INFO    : There is nothing to migrate
2025-03-05 00:38:01.025131706  [2025-03-05 00:38:01] frigate.app                    INFO    : Recording process started: 379
2025-03-05 00:38:01.030169628  [2025-03-05 00:38:01] frigate.app                    INFO    : Review process started: 388
2025-03-05 00:38:01.031856953  [2025-03-05 00:38:01] frigate.app                    INFO    : go2rtc process pid: 97
2025-03-05 00:38:01.041249369  [2025-03-05 00:38:01] detector.ov                    INFO    : Starting detection process: 395
2025-03-05 00:38:01.049687930  [2025-03-05 00:38:01] frigate.app                    INFO    : Output process started: 411
2025-03-05 00:38:01.179432018  [2025-03-05 00:38:01] frigate.app                    INFO    : Camera processor started for DoorWay_Camera: 436
2025-03-05 00:38:01.185796528  [2025-03-05 00:38:01] frigate.app                    INFO    : Camera processor started for Home_Camera: 437
2025-03-05 00:38:01.195865146  [2025-03-05 00:38:01] frigate.app                    INFO    : Camera processor started for Pet_Camera: 440
2025-03-05 00:38:01.207520830  [2025-03-05 00:38:01] frigate.app                    INFO    : Capture process started for DoorWay_Camera: 448
2025-03-05 00:38:01.254715677  [2025-03-05 00:38:01] frigate.app                    INFO    : Capture process started for Home_Camera: 491
2025-03-05 00:38:01.265019557  [2025-03-05 00:38:01] frigate.app                    INFO    : Capture process started for Pet_Camera: 495
2025-03-05 00:38:01.320440210  [2025-03-05 00:38:01] frigate.audio_manager          INFO    : Audio processor started (pid: 502)
2025-03-05 00:38:02.144888840  [2025-03-05 00:38:02] frigate.api.fastapi_app        INFO    : Starting FastAPI app
2025-03-05 00:38:02.246269256  [2025-03-05 00:38:02] frigate.api.fastapi_app        INFO    : FastAPI started

It seems that there is no abnormality

When I changed the configuration file to an online solution, that is


detectors:
ov:
type: openvino
device: GPU

The startup log is as follows:


2025-03-05 00:46:09.512720925  [2025-03-05 00:46:09] frigate.app                    INFO    : Capture process started for DoorWay_Camera: 433
2025-03-05 00:46:09.573390424  [2025-03-05 00:46:09] frigate.app                    INFO    : Capture process started for Home_Camera: 456
2025-03-05 00:46:09.583395985  [2025-03-05 00:46:09] frigate.app                    INFO    : Capture process started for Pet_Camera: 460
2025-03-05 00:46:09.641377941  [2025-03-05 00:46:09] frigate.audio_manager          INFO    : Audio processor started (pid: 465)
2025-03-05 00:46:10.726081636  [2025-03-05 00:46:10] frigate.api.fastapi_app        INFO    : Starting FastAPI app
2025-03-05 00:46:11.004073114  [2025-03-05 00:46:11] frigate.api.fastapi_app        INFO    : FastAPI started
2025-03-05 00:46:20.441681288  [2025-03-05 00:46:20] frigate.video                  ERROR   : Home_Camera: Unable to read frames from ffmpeg process.
2025-03-05 00:46:20.441998015  [2025-03-05 00:46:20] frigate.video                  ERROR   : Home_Camera: ffmpeg process is not running. exiting capture thread...
2025-03-05 00:46:29.602550032  [2025-03-05 00:46:29] watchdog.Home_Camera           ERROR   : Ffmpeg process crashed unexpectedly for Home_Camera.
2025-03-05 00:46:29.602726002  [2025-03-05 00:46:29] watchdog.Home_Camera           ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
2025-03-05 00:46:29.602885555  [2025-03-05 00:46:29] ffmpeg.Home_Camera.detect      ERROR   : [h264 @ 0x557ad1800a00] Using possibly-incompatible profile 100 instead.
2025-03-05 00:46:29.603021341  [2025-03-05 00:46:29] ffmpeg.Home_Camera.detect      ERROR   :     Last message repeated 1 times
2025-03-05 00:46:29.603164348  [2025-03-05 00:46:29] ffmpeg.Home_Camera.detect      ERROR   : [segment @ 0x557ad1433d80] Timestamps are unset in a packet for stream 0. This is deprecated and will stop working in the future. Fix your code to set the timestamps properly
2025-03-05 00:46:29.603294944  [2025-03-05 00:46:29] ffmpeg.Home_Camera.detect      ERROR   : [aac @ 0x557ad1400300] Queue input is backward in time
2025-03-05 00:46:29.603420187  [2025-03-05 00:46:29] ffmpeg.Home_Camera.detect      ERROR   :     Last message repeated 5 times
2025-03-05 00:46:29.603546623  [2025-03-05 00:46:29] ffmpeg.Home_Camera.detect      ERROR   : [rtsp @ 0x557ad13c9580] RTP H.264 NAL unit type 29 is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented.
2025-03-05 00:46:29.603661928  [2025-03-05 00:46:29] ffmpeg.Home_Camera.detect      ERROR   : [rtsp @ 0x557ad13c9580] RTP: PT=60: bad cseq e3e5 expected=d240
2025-03-05 00:46:29.603781213  [2025-03-05 00:46:29] ffmpeg.Home_Camera.detect      ERROR   : [h264 @ 0x557ad18406c0] Invalid NAL unit 0, skipping.
2025-03-05 00:46:29.603908087  [2025-03-05 00:46:29] ffmpeg.Home_Camera.detect      ERROR   : [AVHWFramesContext @ 0x7fe4280b8b00] Failed to sync surface 0xb: 23 (internal decoding error).
2025-03-05 00:46:29.604009420  [2025-03-05 00:46:29] ffmpeg.Home_Camera.detect      ERROR   : [hwdownload @ 0x7fe434003980] Failed to download frame: -5.
2025-03-05 00:46:29.604152648  [2025-03-05 00:46:29] ffmpeg.Home_Camera.detect      ERROR   : [vf#1:0 @ 0x557ad14461c0] Error while filtering: Input/output error
2025-03-05 00:46:29.604267929  [2025-03-05 00:46:29] ffmpeg.Home_Camera.detect      ERROR   : [vf#1:0 @ 0x557ad14461c0] Task finished with error code: -5 (Input/output error)
2025-03-05 00:46:29.604387645  [2025-03-05 00:46:29] ffmpeg.Home_Camera.detect      ERROR   : [vf#1:0 @ 0x557ad14461c0] Terminating thread with return code -5 (Input/output error)
2025-03-05 00:48:14.450923874  [2025-03-05 00:48:14] frigate.record.maintainer      WARNING : Too many unprocessed recording segments in cache for Pet_Camera. This likely indicates an issue with the detect stream, keeping the 6 most recent segments out of 7 and discarding the rest...
2025-03-05 00:48:24.460121837  [2025-03-05 00:48:24] frigate.record.maintainer      WARNING : Too many unprocessed recording segments in cache for Pet_Camera. This likely indicates an issue with the detect stream, keeping the 6 most recent segments out of 7 and discarding the rest...
2025-03-05 00:48:24.460728059  [2025-03-05 00:48:24] frigate.record.maintainer      WARNING : Too many unprocessed recording segments in cache for DoorWay_Camera. This likely indicates an issue with the detect stream, keeping the 6 most recent segments out of 7 and discarding the rest...
2025-03-05 00:48:34.467999798  [2025-03-05 00:48:34] frigate.record.maintainer      WARNING : Too many unprocessed recording segments in cache for Pet_Camera. This likely indicates an issue with the detect stream, keeping the 6 most recent segments out of 7 and discarding the rest...
2025-03-05 00:48:34.469104848  [2025-03-05 00:48:34] frigate.record.maintainer      WARNING : Too many unprocessed recording segments in cache for DoorWay_Camera. This likely indicates an issue with the detect stream, keeping the 6 most recent segments out of 7 and discarding the rest...
2025-03-05 00:48:44.476689348  [2025-03-05 00:48:44] frigate.record.maintainer      WARNING : Too many unprocessed recording segments in cache for Pet_Camera. This likely indicates an issue with the detect stream, keeping the 6 most recent segments out of 7 and discarding the rest...
2025-03-05 00:48:44.476955195  [2025-03-05 00:48:44] frigate.record.maintainer      WARNING : Too many unprocessed recording segments in cache for DoorWay_Camera. This likely indicates an issue with the detect stream, keeping the 6 most recent segments out of 7 and discarding the rest...
2025-03-05 00:48:54.477596652  [2025-03-05 00:48:54] frigate.record.maintainer      WARNING : Too many unprocessed recording segments in cache for Pet_Camera. This likely indicates an issue with the detect stream, keeping the 6 most recent segments out of 7 and discarding the rest...
2025-03-05 00:48:54.477801028  [2025-03-05 00:48:54] frigate.record.maintainer      WARNING : Too many unprocessed recording segments in cache for DoorWay_Camera. This likely indicates an issue with the detect stream, keeping the 6 most recent segments out of 7 and discarding the rest...
2025-03-05 00:49:04.484861115  [2025-03-05 00:49:04] frigate.record.maintainer      WARNING : Too many unprocessed recording segments in cache for Pet_Camera. This likely indicates an issue with the detect stream, keeping the 6 most recent segments out of 7 and discarding the rest...
2025-03-05 00:49:04.484930735  [2025-03-05 00:49:04] frigate.record.maintainer      WARNING : Too many unprocessed recording segments in cache for DoorWay_Camera. This likely indicates an issue with the detect stream, keeping the 6 most recent segments out of 7 and discarding the rest...
2025-03-05 00:49:14.501302353  [2025-03-05 00:49:14] frigate.record.maintainer      WARNING : Too many unprocessed recording segments in cache for Pet_Camera. This likely indicates an issue with the detect stream, keeping the 6 most recent segments out of 7 and discarding the rest...
2025-03-05 00:49:14.501558138  [2025-03-05 00:49:14] frigate.record.maintainer      WARNING : Too many unprocessed recording segments in cache for DoorWay_Camera. This likely indicates an issue with the detect stream, keeping the 6 most recent segments out of 7 and discarding the rest...
2025-03-05 00:49:24.501296648  [2025-03-05 00:49:24] frigate.record.maintainer      WARNING : Too many unprocessed recording segments in cache for Pet_Camera. This likely indicates an issue with the detect stream, keeping the 6 most recent segments out of 7 and discarding the rest...
2025-03-05 00:49:24.501451212  [2025-03-05 00:49:24] frigate.record.maintainer      WARNING : Too many unprocessed recording segments in cache for DoorWay_Camera. This likely indicates an issue with the detect stream, keeping the 6 most recent segments out of 7 and discarding the rest...
2025-03-05 00:49:34.516731295  [2025-03-05 00:49:34] frigate.record.maintainer      WARNING : Too many unprocessed recording segments in cache for Pet_Camera. This likely indicates an issue with the detect stream, keeping the 6 most recent segments out of 7 and discarding the rest...
2025-03-05 00:49:34.517656961  [2025-03-05 00:49:34] frigate.record.maintainer      WARNING : Too many unprocessed recording segments in cache for DoorWay_Camera. This likely indicates an issue with the detect stream, keeping the 6 most recent segments out of 7 and discarding the rest...

hawkeye217 Mar 4, 2025
Collaborator

See the FAQ, Upgrade Issues question 1.

Answer selected by hawkeye217

zhuzhuani Mar 5, 2025
Author

See the FAQ, Upgrade Issues question 1.

Thanks for the guidance! I followed the FAQ and tried replacing hwaccel_args with preset-intel-qsv-h264 or preset-intel-qsv-h265, but neither worked. Switching back to the original preset-vaapi and adding path: "5.0" resolved the issue.

Questions:

Does this imply that my Intel UHD 630 iGPU is no longer compatible with ffmpeg 7?
Is hardware upgrade the only way to support the latest config profiles?

hawkeye217 Mar 5, 2025
Collaborator

Great, glad it's working for you now.

It seems like there is some older hardware that doesn't work with ffmpeg 7's QSV implementation. We don't intend to remove ffmpeg 5 from the Frigate container, so a hardware upgrade is not strictly necessary.

zhuzhuani · 2025-03-05T13:58:47Z

zhuzhuani
Mar 5, 2025
Author

Thanks for clarifying! I'll hold off on considering hardware upgrades for now.
Appreciate your help again – have a great day! 🌟

1 reply

hawkeye217 Mar 5, 2025
Collaborator

Happy to help!

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Please everyone:Why do I find that the usage rate of Detector CPU is very high after running the latest version of frigate, between 100% and 200%? Is this a normal situation? #16944

Uh oh!

{{title}}

Uh oh!

Replies: 2 comments 5 replies

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Uh oh!

Please everyone:Why do I find that the usage rate of Detector CPU is very high after running the latest version of frigate, between 100% and 200%? Is this a normal situation? #16944

Uh oh!

zhuzhuani Mar 4, 2025

Here is my frigate configuration file

The following is the Docker composed file:

My configuration is CPU: 10100 GPU is the core display of CPU, i.e. UHD630

After searching for various solutions online, I tried a method to configure the frigate

replace with：

Requesting your assistance！

Replies: 2 comments · 5 replies

Uh oh!

hawkeye217 Mar 4, 2025 Collaborator

Uh oh!

zhuzhuani Mar 4, 2025 Author

thanks!

When the content of the configuration file is the first situation I mentioned, the startup log occupies 100% to 200% as follows:

It seems that there is no abnormality

When I changed the configuration file to an online solution, that is

Uh oh!

hawkeye217 Mar 4, 2025 Collaborator

Uh oh!

zhuzhuani Mar 5, 2025 Author

Questions:

Uh oh!

hawkeye217 Mar 5, 2025 Collaborator

Uh oh!

zhuzhuani Mar 5, 2025 Author

Uh oh!

hawkeye217 Mar 5, 2025 Collaborator

zhuzhuani
Mar 4, 2025

Replies: 2 comments 5 replies

hawkeye217
Mar 4, 2025
Collaborator

zhuzhuani Mar 4, 2025
Author

hawkeye217 Mar 4, 2025
Collaborator

zhuzhuani Mar 5, 2025
Author

hawkeye217 Mar 5, 2025
Collaborator

zhuzhuani
Mar 5, 2025
Author

hawkeye217 Mar 5, 2025
Collaborator