Plex Client on Nvidia Shield restarting

Server Version#: 1.40.2.8395
Player Version#: 10.16.0.758

Need some help here.
PMS Version 1.40.2.8395 on Windows 11
Plex Client on Nvidia Shield Version 10.16.0.758

I’ve been culling thru my demo clips (~150) looking to narrow down the library. I’ve played these clips dozens of times w/o problems (clips with problems are quickly trashed).

Now I’m experiencing a situation where every N clips, the PLEX client won’t start the clip, just gives me the spinning circle and after a couple of minutes, the Client reboots and after I sign back in and go to the same video, it plays fine. To me, that smells like a memory leak. I did clear cache and data and restarted Plex, went thru the whole sign in/set up process, but the problem persists.

The only recent change I made was to the Plex client was to set Resolution Switching ON, in response to some Video stuttering watching Jurassic World Dominion last night, and seeing a similar issue a couple of nights ago (first time I can recall) watching Meg 2. I did a brief check after making that change with the scene on Dominion, I last saw the issue played fine.

Let me add, after playing around some, I can create this situation by playing a clip and then quickly backing out (Return, return) to the library screen. If I do that for 3 - 5 clips, the next one hangs and I get the Plex client reboot. This is what I was doing in going thru clips, since I know them fairly well, I will see a few seconds then quicky back out to looks at the next one… Still smells to me like some type of timing bug that leads to a memory leak). Would such a thing even show up in a server log? Is there a client side log for Plex on Nvidia Shield? Attaching latest server log should coinicde with the last problem I generated.
Plex Media Server.log (1.9 MB)

If you disable resolution switching does it still happen?

Yes there is an android TV log

I will have to try that at some point… though if it brings back 4K Video stuttering, I’m not sure it’s a good trade-off. But worth knowing anyway.

Sorry, I did not mean it as some sort of workaround. Just curious if it only happens in that case with it enabled to narrow down trying to reproduce and find where the issue is.

No problem, it makes sense to at least know if that’s causing the problem, then have to explore why and if there’s a solution to the 4K stutter.

I did try turning resolution switching off. Not very scientific, but I could not reproduce the problem over 10 minutes, but with it on, I struggled to reproduce the problem - twice (I think) in 20+ minutes). However I could only capture one in the client log due to log rolling off the first incident so I could not see if their was a common set of log elements. I’ll leave both settings OFF for now, but certainly want to see if the 4K stutter becomes a recurring issue and I have to address that.