[Support]: frigate crashed #22396
Replies: 3 comments 10 replies
-
|
Your logs show two distinct issues that occurred before the crash: 1. Missing Preview Data (Non-Fatal Errors)The 2. Fatal Python GIL Error (The Actual Crash)The crash itself was caused by: This is a low-level Python threading error that occurred during garbage collection. The stack trace shows it happened while the main thread was running the uvicorn server and garbage collection was triggered. RecommendationsFor the preview errors: These are expected for some events and shouldn't cause crashes on their own. Some events simply don't have preview data available. For the GIL crash: This type of crash is typically related to:
Since you're running on a Raspberry Pi with HAOS, consider:
If crashes continue, you may want to check GitHub for similar reports or open a new issue with your logs. 📚 Sources:
Have another question? Just tag @inkeep. |
Beta Was this translation helpful? Give feedback.
-
|
any feedback on this? |
Beta Was this translation helpful? Give feedback.
-
We have not seen this before, are you seeing this often? |
Beta Was this translation helpful? Give feedback.
-
|
Hi,
thank you for the reply,
no just once for this crash
best C.
Cristiano De Michele
***@***.***
… Il giorno 13 mar 2026, alle ore 13:57, Nicolas Mowen ***@***.***> ha scritto:
2026-03-12 05:55:16.046407368 Fatal Python error: PyThreadState_Get: the function must be called with the GIL held, but the GIL is released (the current Python thread state is NULL)
2026-03-12 05:55:16.046412961 Python runtime state: initialized
We have not seen this before, are you seeing this often?
—
Reply to this email directly, view it on GitHub <#22396 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADU4YGSTLNG6MM4S5JI2WT34QQAUTAVCNFSM6AAAAACWPKRWNOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMMJRG43DSNA>.
You are receiving this because you authored the thread.
|
Beta Was this translation helpful? Give feedback.
-
|
...it just happened again a similar error but without a frigate crash, log is attached |
Beta Was this translation helpful? Give feedback.
-
|
There are two errors in your logs - one is related to previews, which is probably fixed by this PR that will be part of 0.17.1. That log message is not what is crashing Frigate. The message near the end of your log related to |
Beta Was this translation helpful? Give feedback.
-
|
ok thank you for the explanation best C. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, best C. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for following up. It seems like this might be caused by a known bug in lxml, the library used for ONVIF communication. When Python's garbage collector runs at the wrong moment, it tries to clean up lxml objects in a way that isn't thread-safe, which brings down the whole process. We haven't seen any other reports of this. This is a rare upstream bug in lxml/CPython 3.11 and not specific to RPi, though the slower CPU and ARM memory model make it more likely to trigger there. Frigate is currently pinned to Python 3.11 across all images, so there's no user-side fix beyond disabling ONVIF if you don't need it. |
Beta Was this translation helpful? Give feedback.
-
|
ok since I do not need ONVIF for now I keep it disabled, |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Checklist
Describe the problem you are having
frigate abruptly crashed
Steps to reproduce
it happened randomly apparently during normal operation
Version
chrome (145.0.7632.160 (Build ufficiale) (arm64))
In which browser(s) are you experiencing the issue with?
No response
Frigate config file
docker-compose file or Docker CLI command
I am using frigate in HAOSRelevant Frigate log output
Relevant go2rtc log output
I do not have this outputOperating system
Home Assistant OS
Install method
Home Assistant Add-on
Network connection
Wireless
Camera make and model
ezviz C8C and C8c 1080p
Screenshots of the Frigate UI's System metrics pages
Any other information that may be helpful
processor usage during crash
memory usage during crash
Beta Was this translation helpful? Give feedback.
All reactions