[Support]: Frigate 0.14.1 keeps crashing with segmentation fault #14458
-
Checklist
Describe the problem you are havingWhen my setup pulled 0.14.1 I started getting errors like this:
similar to Steps to reproduce
Versiondocker image tag 0.14.1 caused issued In which browser(s) are you experiencing the issue with?No response Frigate config file# https://frigate.xxx.com/api/config/schema.json
# https://www.homeautomationguy.io/blog/home-assistant-tips/tweaking-frigate-to-get-the-best-results
ffmpeg:
hwaccel_args: preset-vaapi
output_args:
record: preset-record-generic-audio-aac
snapshots:
enabled: true
go2rtc:
streams:
reolink: rtsp://stream:XXXXXXXXXXXXXXXXXXX@XXXXXXXXXXXXXXXXXXX:554/h265Preview_01_main
reolink-cx810-garage: rtsp://stream:XXXXXXXXXXXXXXXXXXX@XXXXXXXXXXXXXXXXXXX:554/h265Preview_01_main
webrtc:
candidates:
- XXXXXXXXXXXXXXXXXXX:8555
detect:
enabled: true
fps: 5
stationary:
threshold: 10
objects:
track:
- person
record:
enabled: true
retain:
days: 15
mode: all
events:
pre_capture: 3
post_capture: 6
retain:
mode: all
default: 15
# Cams start
cameras:
reolink:
# for better facial recognition
mqtt:
timestamp: false
bounding_box: false
crop: true
quality: 100
height: 600 # should match double-take frigate section
ffmpeg:
inputs:
- path: rtsp://stream:XXXXXXXXXXXXXXXXXXX@XXXXXXXXXXXXXXXXXXX:554/h265Preview_01_main
input_args: preset-rtsp-restream
roles:
- record
- path: rtsp://stream:XXXXXXXXXXXXXXXXXXX@XXXXXXX:554/XXXXXXXXXXXXXXXXXXX #use main as test for face detection
input_args: preset-rtsp-restream
roles:
- detect
objects:
track:
- person
- car
filters:
car:
mask: 0.384,0.166,0.576,0.144,0.617,0.247,0.384,0.278
ui:
order: 0
reolink-cx810-garage:
# for better facial recognition
mqtt:
timestamp: false
bounding_box: false
crop: true
quality: 100
height: 600 # should match double-take frigate section
ffmpeg:
inputs:
- path: rtsp://stream:XXXXXXXXXXXXXXXXXXX@XXXXXXXXXXXXXXXXXXX:554/h265Preview_01_main
input_args: preset-rtsp-restream
roles:
- record
- path: rtsp://stream:XXXXXXXXXXXXXXXXXXX@XXXXXXXXXXXXXXXXXXX:554/h264Preview_01_main #use main as test for face detection
input_args: preset-rtsp-restream
roles:
- detect
objects:
track:
- person
- car
filters:
car:
mask: 0.124,0.124,0,0.202,0,0.298,0.127,0.202
ui:
order: 0
# Cams end
detectors:
#cpu1:
# type: cpu
# num_threads: 2
coral:
type: edgetpu
device: usb
mqtt:
host: mosquitto
version: 0.14
camera_groups:
Main:
order: 1
icon: LuCar
cameras:
- reolink
- reolink-cx810-garage docker-compose file or Docker CLI commandx-common-env: &common-env
environment:
- PUID=${DOCKER_COMPOSE_PUID:?missing-env}
- PGID=${DOCKER_COMPOSE_PGID:?missing-env}
restart: ${DOCKER_COMPOSE_RESTART_VALUE:?missing-env}
mem_limit: ${DOCKER_COMPOSE_MEM_LIMIT_HUGE:?missing-env}
services:
frigate:
<<: *common-env
image: ghcr.io/blakeblackshear/frigate:0.14.1
container_name: frigate
shm_size: "256mb"
privileged: true # needed for Intel VGA
devices:
- /dev/dri/renderD128:/dev/dri/renderD128
- /dev/bus/usb:/dev/bus/usb
- /dev/dri:/dev/dri # hardware acceleration
volumes:
- /etc/localtime:/etc/localtime:ro
- ./config.yaml:/config/config.yml
- ${DOCKER_COMPOSE_STATEFUL_VOLUMES_ROOT:?missing-volume}/frigate/config:/config
- ${DOCKER_COMPOSE_QNAP_VOLUMES_ROOT:?missing-volume}/frigate/storage:/media/frigate
- type: tmpfs # 1GB of memory
target: /tmp/cache
tmpfs:
size: 1000000000
ports:
- "5000:5000" # Port used by the Web UI
- "8554:8554" # RTSP feeds
- "8555:8555/tcp" # WebRTC over tcp
- "8555:8555/udp" # WebRTC over udp
- "1935:1935" # RTMP feeds
environment:
FRIGATE_RTSP_PASSWORD: ${DOCKER_COMPOSE_DEFAULT_PASSWORD:?missing-password}
cap_add:
- CAP_PERFMON
networks:
- nvr-network
- mosquitto-network Relevant Frigate log outputN/A crashes immediately, docker log output is included Relevant go2rtc log outputN/A crashes immediately, docker log output is included Operating systemDebian Install methodDocker Compose Network connectionWired Camera make and modelReolink Screenshots of the Frigate UI's System metrics pagesWas unavailable Any other information that may be helpful0.14.1 is the problem, switched back to 0.14.0 and everything back to normal. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
Nothing changed with that file so it is not clear why this would be an issue, the line that is being pointed to is also not an actual line it's possible that there is a conflict on the config volume definition as they overlap, but that is just a guess. We have not had reports of this issue. What is the host OS? |
Beta Was this translation helpful? Give feedback.
So this is weird, I am not sure what is going on, but I did some copies to create a new container to test your mapping and it passed, but however going back to my main setup and now pushing back to 0.14.1 And it started working!! Without that error.
I double checked that there is no overlap on any volumes...
So for the time being this is resolved, but how, no clue.