2024-09-18, 06:09 PM
I am encountering a weird issue where I get a gray screen with no way to do anything else once I invoke playback of any video on my LG OLED77C21LA at firmwareVersion 13.30.85 and sdkVersion 8.3.0. Once I pick some content to play, I see a very brief spinner as the metadata is getting fetched and then the display immediately switches to gray. The only action I can do at that point is to press the "back" button on the remote and kill the app. The jellyfin app otherwise appears to be working perfectly fine up to that point.
I'm pretty sure this is not related to transcoding problems: if I access jellyfin through the TV's built-in web browser, jellyfin and playback work just fine. Furthermore, I believe the app fails even before it initiates the playback session proper. The only difference between these two contexts is that the app's jellyfin is inside an iframe.
I have tried debugging the app with the inspector and I am not seeing any errors at all when this occurs. One thing that I do see, however, is that the iframe's #document becomes empty. I don't see any javascript errors, and no breakpoints are triggered when I ask the debugger to break on uncaught exceptions. The inspector is somewhat funky, though, so I'm not sure how reliable this is. More curious is that I also don't see the app getting to the point where the usual http requests for playback are initiated. There's the bitrate test, fetch for some styles (e.g.
I have considered that this might be a memory consumption problem, but restart the TV by pulling out power and plugging it back in does not help, unfortunately.
I'm not sure when the problem started -- I'm not using jellyfin on the TV very often. First I noticed this problem is with 10.9.7, but 10.9.11 also has this problem. The app itself is at 1.2.2 from homebrew store.
Has anybody seen anything of a similar sort?
I'm pretty sure this is not related to transcoding problems: if I access jellyfin through the TV's built-in web browser, jellyfin and playback work just fine. Furthermore, I believe the app fails even before it initiates the playback session proper. The only difference between these two contexts is that the app's jellyfin is inside an iframe.
I have tried debugging the app with the inspector and I am not seeing any errors at all when this occurs. One thing that I do see, however, is that the iframe's #document becomes empty. I don't see any javascript errors, and no breakpoints are triggered when I ask the debugger to break on uncaught exceptions. The inspector is somewhat funky, though, so I'm not sure how reliable this is. More curious is that I also don't see the app getting to the point where the usual http requests for playback are initiated. There's the bitrate test, fetch for some styles (e.g.
GET /web/htmlVideoPlayer-style-scss.css), the app opens a /socket and then its gone.I have considered that this might be a memory consumption problem, but restart the TV by pulling out power and plugging it back in does not help, unfortunately.
I'm not sure when the problem started -- I'm not using jellyfin on the TV very often. First I noticed this problem is with 10.9.7, but 10.9.11 also has this problem. The app itself is at 1.2.2 from homebrew store.
Has anybody seen anything of a similar sort?