Jump to content

Crash with M3U Live TV


Recommended Posts

Posted

Hi, the problem was not solved, at the moment on MacOS 26.6.2 the crash still occurs after about 1 second after live tv (from M3U) channel start.

The backend is TVHeadend, within the single second the TV screen is shown but immediately after all the application crash closing completely.

Following the error from system crash report:

-------------------------------------
Translated Report (Full Report Below)
-------------------------------------
Process:             Emby [3561]
Path:                ..../*/Emby.app/Contents/MacOS/Emby
Identifier:          com.emby.mobile
Version:             2.2.39 (35)
Code Type:           ARM-64 (Native)
Role:                Foreground
Parent Process:      launchd [1]
Coalition:           com.emby.mobile [3198]
User ID:             xxx

Date/Time:           2026-08-22 17:22:39.6222 +0200
Launch Time:         2026-08-22 17:20:54.8285 +0200
Hardware Model:      Mac14,13
OS Version:          macOS 26.6.2 (25G83)
Release Type:        User

Crash Reporter Key:  ....
Incident Identifier: ....

Time Awake Since Boot: 32000 seconds

System Integrity Protection: enabled

Triggered by Thread: 42  com.apple.audio.IOThread.client

Exception Type:    EXC_BAD_ACCESS (SIGSEGV)
Exception Subtype: KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Codes:   0x0000000000000001, 0x0000000000000000

Termination Reason:  Namespace SIGNAL, Code 11, Segmentation fault: 11
Terminating Process: exc handler [3561]
 

sa2000
Posted

I split your post into a new topic as the specific issue you added your post to has already been resolved and related to subtitles

I see the above crash report is for Emby for MacOS 2.2.39. Could you please try with the latest version of Emby for MacOS available on the MacOS app store which should be 2.256

If the problem persists with the latest version, please enable debug logging within the App by going to App Settings / Logs / Settings / Enable App logging. Then shutdown the app and re-launch and reproduce the problem and capture the full crash report and attach together with the Emby for Mac OS app logs which would be in 

~/Library/Containers/com.emby.mobile/Data/Library/Caches/emby_logs

;

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...