Emby Server HardLocks/Crashes after completion of IPTV stream on AndroidTV Clients (Fire/Shield Tested)

[dicion 3]

Latest Emby Server, running on Ubuntu 22.04.5

Emby server locks up and goes nonresponsive first, and then crashes, after ending M3U Based LiveTV Stream on AndroidTV, but not Web browser client.

This has occurred for me on both a NVidia Shield and a Amazon Fire Stick.

Method to recreate:

- Add m3u livetv source., Watch M3U LiveTV Source on AndroidTV Client. Video Streams fine.. no issues so far.
- End LiveTV Stream. Emby server goes nonresponsive, Maxxes out CPU on host, and eventually crashes without restart.

Server logs attached.

LiveTV Stream Ended at 2026-01-07 12:21:43.489 in the attached logs.

Looks like it tries to restart at 12:23:53.948, but.. it is not successful. I had to restart the VM to get it back up.

If you look in ffmpeg-directstream log, it looks like no one told it that it ended, and it just keeps..... going... even though there's nothing to send it to?

 

ffmpeg-directstream-de203edd-f72c-45bc-8c4d-d6cf1ea7b3db_1.txt embyserver-63903388085.txt

[dicion 3]

Conversely, here is logs of me doing the EXACT SAME thing, same channel, everything, in the Web-based client (Chrome) and it NOT crashing


LiveTV Stream ended at 2026-01-07 13:41:02.391

Server... keeps working with no issues whatsoever.

My observations:

The one that DOESN'T crash, has these lines in the next second after "Info SessionManager: Playback stopped" Line
 

2026-01-07 13:41:02.391 Info SessionManager: Playback stopped reported by app Emby Web 4.9.1.90 on Google Chrome Linux playing COL| CANAL TRECE PLUS ᴴᴰ. Position: 54886 ms. PlaySessionId: 3ed7af51e461409e8d675f6292692dd5. IsPaused: False

2026-01-07 13:41:02.392 Info MediaSourceManager: Live stream 80409b37fc1a2d43ddcfb62e20706ca4 consumer count is now 0

2026-01-07 13:41:02.393 Info MediaSourceManager: Closing live stream 06044cf0e6f93cdae5f285c9ecfaaeb4_01413a525b3a9622ce6fdf19f7dde354_80409b37fc1a2d43ddcfb62e20706ca4

2026-01-07 13:41:02.393 Info SharedHttpPipelineSource: Closing SharedHttpPipelineSource

2026-01-07 13:41:02.394 Info SharedHttpPipelineSource: Deleting temp files /m/embybackup/transcode/transcoding-temp/dd323b50a9b24618afdeffda1c303883/0000000.ts

2026-01-07 13:41:02.400 Info MediaSourceManager: Live stream 06044cf0e6f93cdae5f285c9ecfaaeb4_01413a525b3a9622ce6fdf19f7dde354_80409b37fc1a2d43ddcfb62e20706ca4 closed successfully

2026-01-07 13:41:02.400 Info SessionManager: Removed playSession 3ed7af51e461409e8d675f6292692dd5 from session d33ffb2bbd75bae0f463297ac0b7de86

2026-01-07 13:41:02.400 Info PlaystateService-0HNIE40DIOALJ:0000006C: http/1.1 Response 204 to host4. Time: 10ms. POST http://host2/emby/Sessions/Playing/Stopped?X-Emby-Client=Emby Web&X-Emby-Device-Name=Google Chrome Linux&X-Emby-Device-Id=07d7a37d-5eab-4d65-82f9-4e5a8e2f6092&X-Emby-Client-Version=4.9.1.90&X-Emby-Token=x_secret7_x&X-Emby-Language=en-us&reqformat=json.

2026-01-07 13:41:02.401 Info App: ProcessRun 'StreamTranscode 6edc73': Stopping ffmpeg process with q command for /m/embybackup/transcode/transcoding-temp/A5C108/A5C108_0.ts

2026-01-07 13:41:02.401 Info SharedHttpPipelineSource: SharedHttpPipelineSource is done streaming.

2026-01-07 13:41:02.402 Info LiveStreamService-0HNIE40DIOAOT:00000001: http/1.1 Response 200 to 127.0.0.1. Time: 55408ms. GET http://127.0.0.1:8096/LiveTv/LiveStreamFiles/dd323b50a9b24618afdeffda1c303883/stream.ts. Headers: Connection=close, Content-Type=video/mp2t, Date=Wed, 07 Jan 2026 19:40:06 GMT, Server=UPnP/1.0 DLNADOC/1.50, Transfer-Encoding=chunked, Cross-Origin-Resource-Policy=cross-origin, Private-Network-Access-Name=Media ServerSERVER, Private-Network-Access-Id=e034884ec45949f5b684e21d5bcb799e

2026-01-07 13:41:02.409 Info App: AppendExtraLogData - Read graph file: /var/lib/emby/logs/ffmpeg-directstream-6edc73fb-99ec-47ce-b510-a3f81d23273b_1graph.txt

2026-01-07 13:41:02.412 Info App: AppendExtraLogData - Deserialized GraphData fileStream: 27.00 bytes Graph Count: 0

2026-01-07 13:41:02.412 Info App: AppendExtraLogData - File Deleted

2026-01-07 13:41:02.434 Info HttpClient: Http response 404 from http://xplatinmedia.com:8080/images/40f7a6523a97ef723d5c0928754b6b49.png after 150ms

2026-01-07 13:41:02.434 Info HttpClient: GET http://xplatinmedia.com:8080/images/40f7a6523a97ef723d5c0928754b6b49.png

2026-01-07 13:41:02.452 Info App: ProcessRun 'StreamTranscode 6edc73' Process exited with code 0

Showing it cleanly closing/ending/whatever all the stuff.

The one that DOES crash does NOT have ANY of those lines that I can see. It does not seem to be cleanly exiting.
 

2026-01-07 12:21:43.489 Info SessionManager: Playback stopped reported by app AndroidTv 2.1.29a on RT's Fire TV playing COL| CANAL TRECE PLUS ᴴᴰ. Position: 445878 ms. PlaySessionId: 5a4be98b414640d0b13b416fae3fcecd. IsPaused: False

*** FOUR SECOND GAP WHERE NOTHING IS LOGGED ***

2026-01-07 12:21:47.215 Info HttpClient: GET http://canalvisiondorada.com.co/images/I_Destacada1024x500.png

 

ffmpeg-transcode-9f38af59-c4e4-4858-a189-7265aa84d6da_1.txt embyserver (1).txt

Edited January 7 by dicion

[Luke 42077]

9 hours ago, dicion said:

Latest Emby Server, running on Ubuntu 22.04.5

Emby server locks up and goes nonresponsive first, and then crashes, after ending M3U Based LiveTV Stream on AndroidTV, but not Web browser client.

This has occurred for me on both a NVidia Shield and a Amazon Fire Stick.

Method to recreate:

- Add m3u livetv source., Watch M3U LiveTV Source on AndroidTV Client. Video Streams fine.. no issues so far.
- End LiveTV Stream. Emby server goes nonresponsive, Maxxes out CPU on host, and eventually crashes without restart.

Server logs attached.

LiveTV Stream Ended at 2026-01-07 12:21:43.489 in the attached logs.

Looks like it tries to restart at 12:23:53.948, but.. it is not successful. I had to restart the VM to get it back up.

If you look in ffmpeg-directstream log, it looks like no one told it that it ended, and it just keeps..... going... even though there's nothing to send it to?

 

ffmpeg-directstream-de203edd-f72c-45bc-8c4d-d6cf1ea7b3db_1.txt 147.26 kB · 0 downloads embyserver-63903388085.txt 1.28 MB · 1 download

Hi, in this first example it looks like you restarted the server in the middle of playback, right?

[dicion 3]

7 hours ago, Luke said:

Hi, in this first example it looks like you restarted the server in the middle of playback, right?

I did not.

In the first example, I started watching the livestream in the AndroidTV Client at 2026-01-07 12:14:15

2026-01-07 12:14:15.597 Info SessionManager: Playback start reported by app AndroidTv 2.1.29a on RT's Fire TV playing COL| CANAL TRECE PLUS ᴴᴰ. Position: 0 ms. PlaySessionId: 5a4be98b414640d0b13b416fae3fcecd. IsPaused: False

And stopped at 2026-01-07 12:21:43.489

2026-01-07 12:21:43.489 Info SessionManager: Playback stopped reported by app AndroidTv 2.1.29a on RT's Fire TV playing COL| CANAL TRECE PLUS ᴴᴰ. Position: 445878 ms. PlaySessionId: 5a4be98b414640d0b13b416fae3fcecd. IsPaused: False

That is the extent of my actions. Whatever happened between those with the server was not done by me.

[Luke 42077]

@dicionhave you updated to Emby Server 4.9.3? Has that helped?

[Luke 42077]

Quote

If you look in ffmpeg-directstream log, it looks like no one told it that it ended, and it just keeps..... going... even though there's nothing to send it to?

How did you stop playback?

[dicion 3]

On 1/18/2026 at 11:37 PM, Luke said:

@dicionhave you updated to Emby Server 4.9.3? Has that helped?

I have updated, I have not tried to recreate as of yet. I will do this soon.

On 1/18/2026 at 11:38 PM, Luke said:

How did you stop playback?

By clicking the back button in the upper left. When I retest with 4.9.3 I will try different methods and report back if it still does it.