Additional debug sent as requested (just posting here so other users know this is still moving).
So glad I found this, my cpu was burring at 100% to 192% and even over 200% at times.
I have downgraded to the recommenced version for now.
Dam its still hitting over 100% with scanning my library, its much less with this version. So that’s a good thing.
Version 1.14.0.5470
I check above for what else I need to do to report this.
CPU Sample of server not transcoder.
Sample of Plex Media Server2.txt (201.2 KB)
2nd sample Sample of Plex Media Server3.txt (1.1 MB)
Also seeing this with the transcoder when I watch a show in safari 12 on my iMac (same system as the server)
I will post the logs after a bit, its still scanning my files
CPU sample of transcoder
Sample of Plex Transcoder.txt (102.6 KB)
Here are the log files
Classic Plex customer service right here.
Request logs, do nothing for months then disappear from the thread. This is happening to mine and a friends server. Makes the whole system unresponsive. Once again they break something and have no clue on how to fix it.
This has been worked on in multiple threads, so I guess it’s unreasonable to expect updates from the Plex team in every thread (I’ve said it before and I’ll say it again: public visibility of bug tracking/tickets would be super helpful).
IMHO, the most productive work on the problem (along with this thread) has been here:
tl;dr Plex started using a new (to them) open source library to parse the XML response from UPnP devices on the LAN and I believe the implementation is responding badly to data provided by routers running the miniupnpd software and going into a CPU loop.
Best current workarounds are to either disable UPnP (no need to disable NAT-PMP, just UPnP) on your router or keep your PMS instance on 1.14.0.5470
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
