blu opened issue starred/frigate-blakeblackshear-2#3863 2026-02-06 11:49:00 -08:00
[Support]: Stream issue since current beta
blu opened issue starred/frigate-blakeblackshear-2#3864 2026-02-06 11:49:00 -08:00
[Support]: MQTT 'available' topic set 'offline' through LWT?
blu opened issue starred/frigate-blakeblackshear-2#3865 2026-02-06 11:49:00 -08:00
[Config Support]: Docker-compose on 13.1 beta
blu closed issue starred/frigate-blakeblackshear-2#3863 2026-02-06 11:49:00 -08:00
[Support]: Stream issue since current beta
blu closed issue starred/frigate-blakeblackshear-2#3864 2026-02-06 11:49:00 -08:00
[Support]: MQTT 'available' topic set 'offline' through LWT?
blu closed issue starred/frigate-blakeblackshear-2#3865 2026-02-06 11:49:00 -08:00
[Config Support]: Docker-compose on 13.1 beta
blu commented on issue starred/frigate-blakeblackshear-2#3863 2026-02-06 11:49:00 -08:00
[Support]: Stream issue since current beta

@NickM-27 commented on GitHub (Sep 15, 2023):

Looks like you're running home assistant integration beta, which wouldn't affect frigates handling of the stream.

So you're saying moving back to…

blu commented on issue starred/frigate-blakeblackshear-2#3862 2026-02-06 11:48:59 -08:00
[Support]: Crash possible memory leak? exited with code 256 (by signal 9)

@skywurz commented on GitHub (Sep 16, 2023):

its been running at 3.5gb - 4.1gb ging up and down properly for awhile now. I believe you have solved it and it was a config issue.

I was trying to…

blu commented on issue starred/frigate-blakeblackshear-2#3861 2026-02-06 11:48:59 -08:00
High CPU after upgrade to 0.13.0 - Make sure to set camera detect resolution

@NickM-27 commented on GitHub (Sep 15, 2023):

I think that should be fine

blu commented on issue starred/frigate-blakeblackshear-2#3861 2026-02-06 11:48:59 -08:00
High CPU after upgrade to 0.13.0 - Make sure to set camera detect resolution

@madasus commented on GitHub (Sep 15, 2023):

thanks - i'll continue to monitor.

blu commented on issue starred/frigate-blakeblackshear-2#3861 2026-02-06 11:48:59 -08:00
High CPU after upgrade to 0.13.0 - Make sure to set camera detect resolution

@NickM-27 commented on GitHub (Sep 15, 2023):

Going to close this since the original issue was solved. Going to leave this pinned at the top of the issues board for now because I foresee other…

blu commented on issue starred/frigate-blakeblackshear-2#3861 2026-02-06 11:48:56 -08:00
High CPU after upgrade to 0.13.0 - Make sure to set camera detect resolution

@NickM-27 commented on GitHub (Sep 15, 2023):

that is just due to the camera resolution auto detection. Just set the detect resolution for each camera and it will be good to go

blu commented on issue starred/frigate-blakeblackshear-2#3862 2026-02-06 11:48:56 -08:00
[Support]: Crash possible memory leak? exited with code 256 (by signal 9)

@NickM-27 commented on GitHub (Sep 15, 2023):

That config has those args for the restream. You are not using the reatream for that input so the query args are wrong in that case.

blu commented on issue starred/frigate-blakeblackshear-2#3862 2026-02-06 11:48:56 -08:00
[Support]: Crash possible memory leak? exited with code 256 (by signal 9)

@skywurz commented on GitHub (Sep 15, 2023):

That config has those args for the restream. You are not using the reatream for that input so the query args are wrong in that case.

Oh!! I see…

blu commented on issue starred/frigate-blakeblackshear-2#3861 2026-02-06 11:48:56 -08:00
High CPU after upgrade to 0.13.0 - Make sure to set camera detect resolution

@madasus commented on GitHub (Sep 15, 2023):

I set it in the main detect section

detect: max_disappeared: 500 width: 1280

Optional: height of the frame for the input with the detect…

blu commented on issue starred/frigate-blakeblackshear-2#3861 2026-02-06 11:48:55 -08:00
High CPU after upgrade to 0.13.0 - Make sure to set camera detect resolution

@NickM-27 commented on GitHub (Sep 15, 2023):

oh wait just kidding I see what the problem is, you have not set your detect resolution, and in 0.13 frigate will auto detect the stream resolution…

blu commented on issue starred/frigate-blakeblackshear-2#3862 2026-02-06 11:48:55 -08:00
[Support]: Crash possible memory leak? exited with code 256 (by signal 9)

@NickM-27 commented on GitHub (Sep 15, 2023):

also noticed on one camera you are using rtsp://xxxxx:PWDxxx@192.168.1.24:554/h264Preview_01_main?video=copy&audio=aac but that is not valid…

blu commented on issue starred/frigate-blakeblackshear-2#3861 2026-02-06 11:48:55 -08:00
High CPU after upgrade to 0.13.0 - Make sure to set camera detect resolution

@madasus commented on GitHub (Sep 15, 2023):

That was it - thank you. Assumed it was something config related.

See a couple of other weird errors in the logs but i'm not even sure what camera…

blu commented on issue starred/frigate-blakeblackshear-2#3862 2026-02-06 11:48:55 -08:00
[Support]: Crash possible memory leak? exited with code 256 (by signal 9)

@skywurz commented on GitHub (Sep 15, 2023):

also noticed on one camera you are using rtsp://xxxxx:PWDxxx@192.168.1.24:554/h264Preview_01_main?video=copy&audio=aac but that is not valid…

blu commented on issue starred/frigate-blakeblackshear-2#3862 2026-02-06 11:48:54 -08:00
[Support]: Crash possible memory leak? exited with code 256 (by signal 9)

@skywurz commented on GitHub (Sep 15, 2023):

also noticed on one camera you are using rtsp://xxxxx:PWDxxx@192.168.1.24:554/h264Preview_01_main?video=copy&audio=aac but that is not valid for…