Segfault in transcoder process with ~2 min left in video

I too have been having this same issue. I migrates from a synology to a bare metal intel nuc11 in hopes it would resolve and continue to have this issue.

1 Like

I’m looking for answers to this as well. I am seeing the error of transcoding failed, but the whole server doesn’t crash, so there are no crash reports in the logs to upload. The best I’ve been able to send it is the debug logs. I have a Synology 720 NAS with the DSM 7, and watching through a Roku Ultra XS 4800. The error starts usually in the final minutes of a movie or TV show. This seems to have started for me since the last PMS release. When it came out, I updated to it, like I do for most new version releases, and this time, it burned me. The Synology won’t let me downgrade, like other users like Windows 10 users have reported being able to do. Anyone finding any workarounds for this or if a fix is in the works within Plex engineering?

For clarification only – Roku Ultra 4800X ? (I don’t find am Ultra 4800XS).
I just purchased the Ultra 4800X

I got it so I can try to replicate the problems being reported.

I’ve not been able to so far.

What can you tell me about the video being played ? ( Maybe I have something here which is close enough which replicates the failure )

This happens on a variety of devices for me. Two TCL TVs as well as several different Roku players. There is nothing remarkable I’ve seen in the sources. H264 1080p videos. The only thing I can maybe say is that the longer the show the better (hour long versus 30 minutes). Yellowstone seems to trigger it every episode. The only thing I can say somewhat conclusively is that it happened right around the release that ffmpeg was upgraded and the new hardware support was added ~6-8 weeks ago. Before that, everything was fine.

1 Like

I’ve just started having this issue as well (since 5319, and upgrading to Roku Ultimate 4800X- I did not see this issue in my older Roku 4), it does not seem to be related to the length of the video (happens in less than 30 min video lengths, 30 Rock for instance), but always in the last <2 minutes of the video length. This seems to be related to Roku, or any device which can direct stream the video, but requires transcoding audio from AAC.

1 Like

@aeriana

Please confirm for me?

  1. If the video is direct play (no video transcode)

  2. And the audio converts to AAC

  3. The transcoder will fault in the last two minutes?

If true, can you get me a sample of the file given you state the it doesn’t seem to be related to overall length ?

1 Like

Hi, I can confirm Plex on Roku Ultimate 4800X shows partial transcode (video direct play, audio EAC3-5.1 unsupported, requires transcode), and the transcode fails at a random point after 2 minutes (even when attempting to skip directly to right after the crash in the <2 minute point).

Link to content - I’ve provided the full video in question, I’m afraid if I attempt to slice it, I might otherwise re-encode it and prevent reduplication of the issue.

Thank you for your help! Let me know if there’s any other helpful information I can provide :blush:

Same thing is happening to me. Upgraded to 1.25.2.5319 and now the transcoder is crashing on a partial conversion of audio.

Trying to convert TRUEHD to EAC. Roku TV, Synology NAS.

Downgrading back to the previous version (https://downloads.plex.tv/plex-media-server-new/1.24.5.5173-8dcc73a59/synology-dsm7/PlexMediaServer-1.24.5.5173-8dcc73a59-x86_64_DSM7.spk) solved the problem. I don’t know why Plex doesn’t allow you to download previous versions but that’s the link. Just uninstall it (it’ll preserve settings) and reinstall using that SPK.

TO ALL FOLLOWING HERE:

  1. Bug found and fixed. (it was a 1 line fix)
  2. :crossed_fingers: it might make this next update of PMS.

NO PROMISES that it will but it makes sense it should given it was an easy fix and which engineer found it.

@ChuckPa any details you can share on what the bug (and the fix) were?

It was quite simple actually,

If the file’s headers state the runtime is longer than it actually is, when you get to end-of-file, pad with blank frames.

Example:

File run time is 100 seconds, FPS = 24p → 2400 frames of video.
However, the header is wrong (rounding) and the actual length of the file is 2397 frames long.

When you get to eof, pad with blank frames which, in this example , is 3 blank frames to fill out the second worth of video.

The transcoder was crashing at 2 minutes before the end because it defaults 2 transcoding 2 minutes ahead of playback requirement.

It would get to the end and find itself those couple frames short of what it needed.

1 Like

Thanks for sharing and getting this figured out! It’s been frustrating and glad to see it will be getting fixed soon!

@ChuckPa thank you for the details!

@ChuckPa Sooooooo is there any way WE can fix this on our servers in the meantime?

1 Like

Just wanted to let you know that i downgraded to this Version and now all my files work from the latest update. I was having issues with EAC 5.1 not playing at all on my synology

There is no way to fix the current released server.

I know the fix is inEngineering’s hands.

Given the severity, I expect it to be in the next release but can’t guarantee it until I see (draft) release notes.

(FYI. I’m writing up a bunch of release notes myself for my work to include in the next release)

1 Like

Is this patch included in 1.25.3.5409?

Please avoid 5409 until further notice.

It’s causes ASUSTOR and QNAP machines to fail to start.
Engineering has been alerted

FWIW I was just about to report the exact same issue. I see there is a fix in the works, and so I will keep my eye on this.

I’ve also had the same issue. I downgraded to 1.24.5 as per Formz post above and that fixed the problem. Be warned though that I lost all my settings and had to rebuild all my libraries.