mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-05-04 18:09:12 +03:00
Random crashes on Apple Silicon macOS, internet-facing (Possible .NET issue) #6661
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @grizzogor on GitHub (Jan 16, 2025).
This issue respects the following points:
Description of the bug
After hosting an internet-facing Jellyfin instance for a couple of days on a headless base model M2 Mac mini, the Jellyfin server will seemingly crash at random times of the day, requiring a click of the "Restart" option in the Menu Bar. When it happens, it shows the following in the logs:
I had looked up the log and it seems to be a .NET issue, resolved 3 days ago in runtime version 9.0.2.
Reproduction steps
What is the current bug behavior?
The Jellyfin Server crashes.
What is the expected correct behavior?
The Jellyfin Server stays up.
Jellyfin Server version
10.10.0+
Specify commit id
No response
Specify unstable release number
No response
Specify version number
No response
Specify the build version
10.10.3
Environment
Jellyfin logs
FFmpeg logs
Client / Browser logs
No response
Relevant screenshots or videos
No response
Additional information
No response
@gnattu commented on GitHub (Jan 16, 2025):
8.0 backport merged 3 days ago: https://github.com/dotnet/runtime/pull/108334, hopefully can be included in dotnet 8.0.13
This is in rare cases that the address returned is empty and dotnet just throws and terminated the main thread but I cannot reproduce on my environment. Maybe you can try disable IPv6 and bind explicitly to an IPv4 address to see if that workarounds this issue at the moment.
@felix920506 commented on GitHub (Feb 16, 2025):
@gnattu it was released in dotnet 8.0.13 https://github.com/dotnet/runtime/releases/tag/v8.0.13
@felix920506 commented on GitHub (Feb 16, 2025):
Closing as this is addressed. A fix will be included in the next Jellyfin release.
@felix920506 commented on GitHub (Feb 17, 2025):
A new release with the fix has been published.
@mstgrv commented on GitHub (Nov 27, 2025):
I'm getting this issue with Jellyfin 10.11.3, was this definitely fixed? Running macOS 26.1, on an M4 mac mini. Jellyfin was still running but couldn't be accessed via the web, had to quit & restart the app to be able to connect again.
The exact log file entry was:
@andreasschmitz commented on GitHub (Jan 13, 2026):
I also still regularly encounter this problem. I am running 10.11.5 on macOS 14.8.3 on an Intel-era Mac mini.