in this case yes but the same thing has happened long after a transcode would have finished and server put to sleep and rewoke. I thought about the transcode maybe existing in my /tmp/ directory still and plex trying to just pick up where it left off on a resume play but that doesnt explain the high CPU usage.
It had never been an issue prior to version 6.9.0-beta35, nvidia drivers (v 455.38), and the new plexinc docker I'm trying (Version 1.21.0.3711) with the HDR tonemapping. Unfortunately I made all the changes at the same time but I know switching back to linuxserver.io's plex container is not the issue because the same issue pops up after waking from S3.
I'm running an Asus Pro WS X570-ACE motherboard with ryzen 3800x CPU and a Quadro P2000 and it was working great on unraid-nvidia but I pushed the update due to the depreciation.
I just tried that flag and it disabled sleep completely, the logs showed the system issuing a wake command after processes failed to suspend. removing it put me back where I was.
I'm going to go digging around in the unraid-nvidia thread some more to see if there's an old post about it somewhere.