Server Version#: 1.18.5.2260
Player Version#: 4.20.1
When a transcode starts that has subtitle burn-in and transcode, the system load starts to spike and climb until it consumes all CPU resources. These netdata screenshots are from a Debian Buster server running on a Ryzen 9 3900X, so 100% cpu usage on 12 cores:
Here you can see someone starts a playback at about 10:55:
You can already see system usage climbing.
Here about 15 min later:
And finally what it’s like now:
Here are the logs, though they don’t seem to show anything out of the ordinary:
Plex Media Server Logs_2020-01-26_11-43-18.zip (1.2 MB)
I first saw this happening about 8-9 months ago, on my old server. It was Debian stretch and a little underpowered. A plex update started causing this problem, so I had to roll back to plexmediaserver_1.15.1.710, which I know for sure did not have this bug. I would periodically update and see if it got fixed, but after a few days someone would play something that caused the system to crash, so I’d roll back again. I ended up running 1.15.1.710 for nearly 6 months until I upgraded my server, so I know for sure it wasn’t present in that build.
After I built my new server I didn’t see the problem for a few months, so I thought it was an issue with my older server. Now I can see that it’s definitely an issue with PMS.
Also, since I last looked, someone else has posted about the same exact issue:
so at least I know it’s not just a weird config with my servers. It has a bit more information, however it doesn’t seem like the post went anywhere
Update:
It seems that my new rig has enough resources to at least avoid a crash. At an arbitrary point in the plaback (about 55% of the way through Zombie Land: Double Tap if it matters), whatever transcoding thread is eating the system resources releases them:
I’ve tested and can see that if I restart plex, and have my friend re-start playback of the same film, the system use starts climbing again.
Also, here is a screen cap with some more information about one of the particular transcodes that causes the problem:







