mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-07-16 05:43:54 +03:00
Playback of transcoded file ends early (response cut off at server side) #3600
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 @Hendi48 on GitHub (Feb 11, 2022).
I'm facing an issue where playback on my client device stops after a couple minutes. Upon investigating a network trace, I found that Kestrel ends the HTTP response with
\r\n0\r\n\r\nafter 0x8590000 bytes have been read from the transcoded file. Incidentally this seems to fit pretty well with the timestamp at which the ffmpeg process ends after finishing transcoding. The file has its full size in the cache dir and is not deleted prematurely. It still exists as of now, 45 minutes after playback was interrupted. I copied the transcode to my local machine and it plays back fine at its full length.I'll do some more digging tomorrow and check whether the interruption really coincides with ffmpeg exiting.
Media Info of the file
Matroska container, 720p h264 video, 2 EAC3 audio tracks, see ffmpeg log below for details.
Logs
FFmpeg Logs
Server System:
Client System:
@Hendi48 commented on GitHub (Feb 11, 2022):
Yes, this is definitely a bug with waiting for the ffmpeg process and then ending the HTTP connection. I sent SIGSTOP to the ffmpeg process to freeze it, and playback on the client continued way past the point where it normally stops.
I was also able to reproduce it with VLC by opening the
stream.tslink there. Stops when ffmpeg is done.@Hendi48 commented on GitHub (Feb 12, 2022):
Regression introduced by
ca887518dd.KeepReadingwill return false when the job has exited, despite there being many bytes left to be read in the stream.@cvium commented on GitHub (Feb 12, 2022):
Thank you for the investigative work
@Mustachipleb commented on GitHub (Jun 18, 2022):
Recently updated to 10.8, where this issue seems to still happen.
Log (Around 13:45 mark):
log_20220618.log
FFMPEG Log:
FFmpeg.Transcode-2022-06-18_13-11-47_69ebb3a677cfe2cd5eb94f65aa03203e_bd006c25.log
Server System:
OS: Docker on Ubuntu 20.04
Jellyfin Version: 10.8.0
Hardware settings & device: Intel Core i7-6700K, HWA with GTX 1070 (Driver ver. 510.73.08)
Reverse proxy: Traefik (Logs are from local playback but problem persists across both proxied and non-proxied connections)
Client System:
Device: AMD Ryzen 5 5600X + RTX 3080
OS: Windows 10 Build 19044
Client: Edge v102.0.1245.41