WebOS client crashes when playing certain videos

[Tristo]

Hey folks,

I've set up a Jellyfin server on my Windows 10 PC (version 10.10.7) and I'm using the Jellyfin client on my LG TV with WebOS (also version 10.10.7).

Most of the media streams perfectly on the WebOS client, but I’ve encountered a specific group of videos that crashes the client, causing the TV to reboot.

The videos that are causing issues have the following specifications (see screenshot #1, which uses the AAC audio codec). For reference, I've included the specifications of another video that streams without any problems (see screenshot #2).

Am I missing something obvious here? If there’s nothing glaring, what would be the best way to debug this issue? Unfortunately, I can't access the logs on the TV, or at least I'm not sure how to.

Thanks for your help!

[bitmap]

Post your Jellyfin and ffmpeg logs using something like privatebin.net.

[raulo1985]

Currently (master branch) JF is using hls.js for the WebOS client in newer LG TV models because of reported playback issues with WebOS native player, but the stable version (10.10.7) is still using the native player. Honestly, I tested JF Web with hls.js and it still had some playback issues in my LG Smart TV (in fact, some that I didn't have previously), so I'm using the native player without much issues. Native player is reported to have some bugs related to using fmp4-hls, and some threads suggest to enable it when using hls.js. If you're using the last stable version without modifications, I would check the fmp4-hls setting and disable it if it's enabled. Fmp4-hls apparently is needed for HEVC and AV1 playback, but I have it disabled and had no issues so far while playing HEVC HDR and SDR movies like the ones in your screenshots.

The other thing is to check your network, to see if something is bottlenecking the bandwith to handle the bitrate of those files (which shouldn't be the case if both files behave differently with similar bitrates).

There's another thing you could try if you know how to build JF from source. Currently there's a new setting available that's only visible using the WebOS client, to use short segments. It can fix some playback issues. Idk if that could be of help regarding your issue, but you could give it a try if you know what you're doing. If you know how to build from source I can tell you which files to modify, so you can enable that setting while keeping JF 10.10.7 (I wouldn't recommend to build the entire JF Web from the master branch. It still has some bugs, at least in my experience. JF 10.10.7 is the most stable and up to date version you should try if you're not helping with debugging). But if you don't know how to build from source and don't have a general understanding of what I said, then maybe it's not a good idea to mess with the source, it could mess your entire setup.

But as stated previously, ffmpeg and JF logs are needed if you need more help.

PS: It's really worth it to learn the basics of Linux, servers are a lot more stable than on Windows in general. Linux Mint or Ubuntu are good distros to start with, specially Linux Mint, since it's pretty similar to Windows, rock solid stable, easy to use and constantly updated. Just a side note.

[Tristo]

I cleared the logs to capture fresh data on the server side, then started the WebOS client and tried to play one of the problematic videos. Unfortunately, I was only able to get this result: https://privatebin.net/?9f3121c50c98502d...v6mq9j2Cwi (personal details redacted).

From what I can tell, the issue does not seem to be on the server side.

I’ve attempted to adjust several options mentioned, such as the HLS container, but nothing has made a difference.

Out of curiosity, I ran one of the problematic videos through Handbrake to transcode it to an MKV H.265 format, using the Fast 1080p30 preset as a starting point. That video played without any issues.

For now, I consider this the solution, unless there's an easy way to retrieve logs from an LG TV for Jellyfin that I can examine.