PlexScriptHost / Plex DLNA Server 100% CPU usage

Server Version#: 1.13.5.5332 (Newest)
Player Version#: N/A

Both “PlexScriptHost.exe” and “Plex DLNA Server.exe” are using a full core of quad core (25% CPU) infinitely. I made a tool too kill them when using ‘100%’ CPU for five minutes. And Plex DLNA Server is starting up every 2 hours. So every 2 hours and 5 minutes it is being killed. PlexScriptHost only did that once after I started the tool, but it will do that multiple (random) times. Not the times I use or watch Plex.

[29.08.18 20:22] Process Plex DLNA Server [19972] KILLED
[29.08.18 22:27] Process Plex DLNA Server [28092] KILLED
[30.08.18 00:32] Process Plex DLNA Server [3688] KILLED
[30.08.18 02:37] Process Plex DLNA Server [27212] KILLED
[30.08.18 04:43] Process Plex DLNA Server [18592] KILLED
[30.08.18 06:48] Process Plex DLNA Server [24224] KILLED

I have probably found the reason, Networx:

Networx does not actively kill any connections as far as I know, it only logs it’s bandwidth usage.

When will the problem be patched that when apparently a connection is killed that the process not goes into a loop?

Kind regards!

Hmm, Now it is all the Plex processes all started to kill the CPU. 100% quad core. Not DLNA only this time.

PlexScriptHost threads overview:
image

Plex DLNA Server overview:
image

The problem is still here. Can anyone give any support?

I’ve already have Debug logging enabled. It still happens every 2 hours with Plex DLNA Server. Besides that I haven’t used it last week.

Nobody will ever react over here?

I’m having the same issue with after around 2 hours of use of Plex server I’m getting 100% CPU usage!

It started after upgrading to Windows 10 version 1809… Before I had run into the same issue when using a VPN connection (Windscribe) and they were kind enough to alter their software to allow it not to close all TCP connections when connecting as a work around option in the product (not as secure but works)… Plex did not address the issue still so I’m rather worried this time round how quickly they might move on this as it seems more users are reporting 100% CPU usage now than ever… hopefully they put this issue to bed once and for all…

Indeed, every 2 hours for DLNA, every now and then for PlexScriptHost.

It should get fixed in Plex.

I’ve just checked and I have DLNA disabled on my Plex setup, the other “PlexScriptHost” you mentioned is that the media scanner that is causing the 100% CPU usage you believe?

I’m not sure if that process is also runned every now and then even if you don’t use Plex and even if no files are changed or added.

C:\WINDOWS\SysWOW64\ucrtbase.dll is the file that is taking the CPU ‘inside’ the Plex DLNA Server.exe process.

I now noticed you can also show the stack inside of the DLL thread. Multiple screenshots:




Hopefully these are helping the developers to fix the issue.

1 Like

I’ve disabled auto library updates and DLNA is also disabled…

I’ve found the PC seemed ok for a number of hours after this change but more testing is needed…

I then found I manually did a library update, all was going well untill I did an update on my photo library at which stage the CPU spiked again as follows:

As you will see below Plex is no longer scanning for images and there is no more disk access (there was when I started the scan but it stopped a few min after the web console reported it has finished scanning but the CPU remains high!)

I then stopped Plex server which free’s up the CPU right away… when reloading plex I started a picture scan again but this time I noticed the CPU usage was only high on the “Plex Media Server.exe” = 25% (which I believe is 1 CPU core being used) and after the scan the CPU usage returned to normally…

I continued to scan other library’s and they all completed fine with no high CPU spike so perhaps the above was just coincidence and would have happened even if I did not start a scan but wanted to report this any way and provide the screenshots in case it’s of help…

Bottom line is I can’t leave Plex running on my system and can only load it up when I want to watch something which is a real pain! Last night I forgot to exit Plex Media Server and when I got home I noticed my study was ‘hot’ as I had the door closed and it must have been running at 100% CPU usage all night and all day :frowning:

Yes… I’ve had that many times… Having plex processes with DAYS of CPU usage… It will get your electricity bill up…

I ran into the same issue last night with the following changes:

  • Disconnect and exit VPN software (Windscribe)
  • Plex DLNA is disable
  • Automatic and periodic library scans are disabled!

After a few hours of idle Plex server made the CPU’s roar upto 100% usage again and I can’t work out why…

Please can someone at Plex help check into this or how can we get support?

Update: Plex server is still causing extreme CPU load… last night before going to bed I loaded up process Explorer and killed the 3x PlexScriptHost.exe processes that were consuming CPU… this caused the CPU on the system to return to normal 0-3% usage…

However just got back home from work today and once again find Plex consuming all my CPU and killing my power bill… Please can this issue be escalated as Plex is essentially not usable…

I noticed this happens to me when I have another DLNA server active on the network (UMS, TVersity, Windows own, BluRay player own). I shut down the machine that runs these servers and it temporarily fixes the problem but if that really is the cause then Plex must fix this.

That is interesting. I think I do have one, but that is on the router delivered from the ISP. You can connect a HDD through USB and it will DLNA for you. I think I will check to see if this is the case and if it is enabled.

Not sure if others are having this issue sill but if so I managed to fix mine at per the following post…

Hope it’s of use to some and keen on your feedback to see if it might help you out as well… I did not manage to narrow down what fixed it but try the same processes one step at a time and you might hopefully find if there is a single cause (Eg, perhaps older Nvidia drivers or similar)… Good luck…

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