-
-
Notifications
You must be signed in to change notification settings - Fork 509
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Jellyfin crashes each time after 5 min when playing a video #1061
Comments
occurs on google tv as well. |
The same thing happens to me, the app restarts, but every 10 minutes or so. |
Similar after a few minutes... |
this seems to be specific to libVLC and the issue is pretty severe, preventing any of our TVs from playing anything |
I figured it out about 10 hours ago, I set to ExoPlayer and everything works fine. |
switching to exo doesn't help - seeking doesn't work. |
It helped me! |
Same, for me it usually happens around 7 minutes. Server logs don't show anything related to the crash/video stopping. |
Attached are the logs from my test session after a fresh restart. I don't have this issue when forcing the app to use ExoPlayer, so I agree it looks like an issue with VLC. |
Did you have to do anything special to reproduce? |
Nope, just started any playback. Happens every time I use libVLC |
I don't really see anything in the provided logs either... |
Logs from current master running with the debugger attached.. From an outsider looking in, it seems to be
Just
All logs (from crash)
|
https://gist.github.com/Artiume/1e206bfc42cc3f50f99d0564c9cd2eaa Here's some more logs for it. I saw it was using libVLC but beyond that, I'm not sure. |
Same here, I've been experiencing this same bug for months now, preventing me from fully migrating from Kodi to Jellyfin...
This is sad... :'( |
Tried version 0.12.1 and still got the same behavior, whatever the backend I use |
This seems to be a pretty common problem, at least common enough to stave off stalebot from mass-closing them.... (Please @nielsvanvelzen , can we not have this stalebot toxicity, especially on issues that have been tagged?) Potentially related: Perhaps the issue should have boundaries drawn and tracked in a single place?
|
Thank you for sharing your concerns @douglasg14b. Unfortunately the Android TV team is really small and we don't have the time to properly triage all issues. We're using stalebot to help with this, the bot will only close if an issue becomes stale. Leaving a comment will prevent the bot from closing. I know this is not an ideal solution (I don't like it myself when this happens on another repository either) but we'll have to do it with what we have. We're 100% aware that there are some major issues with playing video (and audio) in our app. To fix this a complete rewrite of this code is happening as we speak (#1057). The current code is in "maintenance" mode and we will try to fix issues we find (and review/accept pull requests for those fixes and smaller features!). Unfortunately this particular issue is really hard to fix due too the bad state of the code. For example: our implementation using LibVLC is really old and not following the standard API like the official VLC app. I'll see if I can find time later this week to look trough your list and close duplicate issues as needed. I'm quite busy at the moment. |
@nielsvanvelzen I appreciate the reply! Thank you for the explanation. I might suggest making the rewrite a bit more widely known (Pinning can be easily missed, perhaps an issue template thing calling it out?), indicating that these playback issues are known and are probably begin addressed as part of that initiative. Just knowing that a thing is happening can reduce user frustration and sets reasonable expectations, even if timelines are largely unknown. This by extension can reduce load and frustration for devs who know what's happening, but have to constantly put out fires from those who are not aware. |
@nielsvanvelzen Thanks for acknowledging the many playback issues. I was getting increasingly frustrated that these reports were seemingly not getting any attention, and it's great to know it's being worked on. |
Same issue here. Using Traefik and Android TV |
Are you using the latest beta? |
@mueslimak3r the beta fixed it for me. Maybe we should make a release because jellyfin is unusable on androidtv with this bug. |
A 0.13 release is planned "soon" which is why there are currently beta releases available for testing. 😉 |
@thornbill ok that sounds good :) |
That's great to see that u guys took the time to fix this, I might test the beta version if I can, if not I'll wait for the release 👍 |
Still happening for me on master (both VLC and Exo):
|
please provide the full log from that session |
Here you go: https://gist.github.com/ringus1/98eb97688918eedfeed27f6eff08dfc2 Using it on CCWGTV. |
I see this in the log: I wonder how you have your hardware acceleration settings configured on your server, and if perhaps that could be causing an issue.
I don't understand. Does it happen for just this video, some videos, or all videos? Since this is happening with exoplayer too, can you record some logs of that? Some details about the media you're playing would be helpful too. You can get that from |
I'm using 10.8.0alpha with AMD VAAPI. Though, the output file from ffmpeg on server works perfectly fine with local VLC. No stops/incomplete conversion. Same video (with transcoding) works fine via WWW and Kodi. It's the Jellyfin APK that reports stopping of playback:
This issue occurs for some transcoded videos. Direct play works fine with every file that's elligible for it.
I've found at least 2 very different files with this issue, here is one:
I'll add also logs from Exoplayer soon. |
Oddly, I can't replicate that with Exo now. Seems I might have had some cached dependencies or something when building from master previously. ExoPlayer seems to be playing those faulty files with no issues now. Problem looks to be limited to VLC which uses stream.mkv way (though, as mentioned only for some videos) unlike Exo fMP4-HLS / HLS (working both with HEVC and H264 encoding). |
tbh that sounds like this issue since it's transcoded -> mkv: it's discussed here too: I've seen this many times while testing using libVLC, and exo too when I've testing playing mkv transcodes in dev builds. I'm going to be testing replacing fMP4 (HLS) with TS (HLS) for exoplayer so we get back AC-3 audio support when transcoding (mp4 doesn't support it). And when I do that I'll also test using TS (http) for libVLC, and perhaps switching away from mkv (http) will fix it. |
Yeah, it looks to be more related to transcoding to MKV issue you mentioned. TS doesn't support HEVC though, right? Please keep that functionality though 🙂 |
I wanted to try the last beta release, i copied it from a usb key on my Nvidia Shield, but when I try to install it (via ES Explorer), it says "App was not installed"... Should I uninstall the current version first? |
Yeah, if you install the release version from APK you have to uninstall the app store version. You can also sign up for the beta via the app store: |
Well, thanks for the tip, I successfully installed the beta after uninstalling the play store one, and... IT WORKS! congrats and thanks for the fix 😃 but... the only thing is, I can't make subtitle to work now, but I'm not sure if this is relative to the subject (both included SRT and PGS subtitles failed to display) |
please open a new issue for this, and make sure to fully fill out the issue template. |
MPEG transport stream (.ts) supports hevc. Here's a table of containers and codecs they support: I tested using TS instead of MKV for libVLC transcodes, and the issue mentioned above still happens. So a fix won't be as simple as switching containers. |
@mueslimak3r @nielsvanvelzen @bmillemathias Android 5.1.1/7/9 system playback with libVLC is the same issue in Ver0.13 beta4. The client and server appear to be scheduled incorrectly. The exoPlayer is powerful enough to survive the new version. The libVLC continued to hang up. |
I'm still having this issue, not on android TV. I get it both in the web client and in the mac downloaded client. The times that the video playback stops seems relatively random, although i think it increases in frequency as the movie gets closer to the end. Running Jellyfin through unraid via docker. Logs have some similarity to #1183 "slow http response" "error 204" etc (which was closed as dupe of one above). Since I'm not on android, swapping to exoplayer etc isnt really an option as I'm getting it across multiple clients and players Not sure if anyone has any quick fixes before it is resolved? |
This is the exact problem that I am experiencing right now. |
This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments. If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or master branch, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label. This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on Matrix or Social Media. |
Hi! Unfortunately, with the version 0.16 issue is back. On previous version 0.15.12 everything worked properly but after upgrade it plays only for 5 minutes and then crashes. No differ between exoplayer and libvlc and between transcoding or direct steam. |
By total freak chance I have been able to reproduce this issue, unfortunately I have no way to pull logs from the AndroidTV (though debug is enabled). The Jellyfin host logs only show the same playback stopped event over and over (provided here anyway, slightly scrubbed). tl;dr I have seen other people posit this issue was caused by using Wifi but I was not able to reproduce this by switching to a wired connection. Remediation: Restatement of Issue: Logs from Host:
Logs from Client: Configuration TV 1: TV 2: Sofabaton U1: Sony Remote 1, Model: RMF-TX900U (built-in support) Steps:
Tests
|
Describe the bug
Any video media play ends up by jellyfin crashing and restarting after around 5 min.
To Reproduce
Expected behavior
Hmmm not crashing :)
Logs
Don't know how I can provide you that. tell me where they are and I'll provide them
Screenshots
none
System (please complete the following information):
Additional context
no problem with 0.11
The text was updated successfully, but these errors were encountered: