Same resource runaway/crash behavior but on a different PC

Yup, Jellyfin on Roku seems to be fine so that’s my workaround for the time being.

I notice that it seems Plex is trying to transfer the entire file vs “stream” it from my storage which in this case is a NAS. I further assume it is doing so to process it somehow because just transferring a large file does not cause some flavor of a memory leak.

I ran a packet capture of that to see what it looked like. I am using SMB for this and I see a lot of read requests during the transfer. I am not sure how this looks normally with plex but to me it indicates a lot of stopping and starting.

Given this happen during transcode and direct play I am not sure what it is plex could be trying to process.

In an interesting turn of events, I now have a similar yet not quite as severe issue with Jellyfin.

I cannot make heads or tails of this given I have completely changed hardware.

I tried disabling transcoding in Plex entirely, but I still get the same.

On my office Roku where this happens most I hard set the Roku’s audio settings from “auto” to “stereo”. Which is what this particular TV is. Roku changed something recently it seems where it will play DD+ even on stereo without transcoding. The Plex app sees this. So if I hard set Roku to stereo, Plex only sees stereo and transcodes the sound. So far this seems to have solved my problem. So in this mode of operation there is no massive network transfer and no memory “leak” until the box crashes.

I will do more testing as my main TV is not stereo.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.