PlexScriptHost.exe CPU usage

Hi all,

I’ve tried googling and found a few old threads but nothing with a solution, my Plex server 0.9.16.6 (Windows 10) has recently started running a Python exe called ‘PlexScriptHost.exe’. It uses about 15% CPU usage at all times, which seems odd, and keeps my CPU fan spinning more than it needs to. I’ve attached my most recent log file, it’s been happening for some time I just hadn’t been able to pinpoint which application was calling python. Anyone know what’s causing this?

Thanks,

I would start by removing third party plugins from: G:\Plex\Plex Media Server\Plug-ins\
If the problem with cpu usage clears up, add them back in one at a time.

Didn’t seem to help, plus the logs all mostly seem to mention the in-built ones. Here’s the two files that are being used by the process (shown at the top of the picture) with CPU hovering at 15% usage. Also attached is the log that is being written (note it never seems to have anything recent, I closed the process (to finish writing the file) at 10:59pm which is about 15 mins after the last entry.

In case anyone is actually interested, I’ve used Process Explorer and determined that it is the ‘system.bundle’ being used while the process is using CPU. I have generate thumbnails turned off in server setting (this was mentioned on a reddit post). Can anyone tell me why Plex is using 15-20% CPU constantly?

There is an outstanding as yet not fixed issue where the PlexScriptHost.exe appears to utilize full cpu when a tcp internal localhost connection is lost. This was established after extensive investigations using process monitor and process explorer

It was also established that the use of a third party product - Networx bandwidth tool - brings the problem on

This of course only applies once you know for sure that there is no actual plex or add-on channels activity that are running and using up CPU

So if I uninstall Networx will the problem go away? The PlexScriptHost.exe is apparently using the plugins system log according to Open File Viewer, but the log never has anything useful (and never even has anything written to it at the time the issue occurs.
Side Note: There seem to be posts going back to 2013 on this with no resolution, and some people seem to encounter 100% CPU usage until they force close Plex. Is the issue being worked on??

@Howchie said:
So if I uninstall Networx will the problem go away? The PlexScriptHost.exe is apparently using the plugins system log according to Open File Viewer, but the log never has anything useful (and never even has anything written to it at the time the issue occurs.
Side Note: There seem to be posts going back to 2013 on this with no resolution, and some people seem to encounter 100% CPU usage until they force close Plex. Is the issue being worked on??

So you are using Networx,

From previous investigations, uninstalling this third party product did stop the loops in PlexScriptHost.exe

The Networx network bandwidth management tool must be killing the tcp sockets for localhost used by PlexScriptHost.exe com.plexapp.system process. When the tcp connections for localhost are lost, it has been proven that PlexScriptHost.exe goes into a loop - this has been raised with the Plex Devs to look into but it is a consequence of something else going wrong - the loss of the internal tcp connection

@sa2000 said:

@Howchie said:
So if I uninstall Networx will the problem go away? The PlexScriptHost.exe is apparently using the plugins system log according to Open File Viewer, but the log never has anything useful (and never even has anything written to it at the time the issue occurs.
Side Note: There seem to be posts going back to 2013 on this with no resolution, and some people seem to encounter 100% CPU usage until they force close Plex. Is the issue being worked on??

So you are using Networx,

From previous investigations, uninstalling this third party product did stop the loops in PlexScriptHost.exe

The Networx network bandwidth management tool must be killing the tcp sockets for localhost used by PlexScriptHost.exe com.plexapp.system process. When the tcp connections for localhost are lost, it has been proven that PlexScriptHost.exe goes into a loop - this has been raised with the Plex Devs to look into but it is a consequence of something else going wrong - the loss of the internal tcp connection

Thanks. Have simply stopped networx from starting with windows, and haven’t seen the process using CPU more than normal since. Networx is useful, but not an essential tool, so I can live without if it saves my CPU from working on an endless loop everyday.

@Howchie said:

@sa2000 said:

@Howchie said:
So if I uninstall Networx will the problem go away? The PlexScriptHost.exe is apparently using the plugins system log according to Open File Viewer, but the log never has anything useful (and never even has anything written to it at the time the issue occurs.
Side Note: There seem to be posts going back to 2013 on this with no resolution, and some people seem to encounter 100% CPU usage until they force close Plex. Is the issue being worked on??

So you are using Networx,

From previous investigations, uninstalling this third party product did stop the loops in PlexScriptHost.exe

The Networx network bandwidth management tool must be killing the tcp sockets for localhost used by PlexScriptHost.exe com.plexapp.system process. When the tcp connections for localhost are lost, it has been proven that PlexScriptHost.exe goes into a loop - this has been raised with the Plex Devs to look into but it is a consequence of something else going wrong - the loss of the internal tcp connection

Thanks. Have simply stopped networx from starting with windows, and haven’t seen the process using CPU more than normal since. Networx is useful, but not an essential tool, so I can live without if it saves my CPU from working on an endless loop everyday.

Does Networx control usage and shutdown connections? does it log any of its activities ?

It’s been a year since I first complained about this process (PlexScriptHost,exe) and its multiple instances (which have a correlated conhost.exe also running at the same time) consuming CPU and memory like an out of control virus or cancer. After a year has the problem been addressed? Apparently not. Has the software become more stable and reliable? No. Do the same issues that existed a year ago still exist? Most definitely, yes. Now, however, not only are there multiple PlexScriptHost.exe/Conhost.exe instances as soon as Plex is started, there are at least 6 instances of PlexMediaScanner.exe as well. I have an 8 core CPU and 32GB of memory and your piece of crap software brings it to a crawl because it is such a complete resource hog. On top of that, it is slower than a snail. No matter how many times a user attempts to close all these multiple instances of scripts, they keep opening up again and again and again along with another conhost.exe. Why in the hell does your program need to open so many command windows in the first place?

Since it’s been a year since I simply had to uninstall Plex because of these resource issues, I’d hoped that these bugs had been worked out. They haven’t so once again I have to go through the pain of uninstalling it again which - though they will NEVER tell you this - actually requires deleting some registry entries manually (more proof the coders are merely script kiddies).

Unfortunately, it seems that no matter what you do PlexScriptHost.exe will ALWAYS be a resource hog because the “coders” (I use that term very loosely here) are nothing but dime-a-dozen run-of-the-mill script kiddies. If they actually had to TYPE and TEST and DEBUG the code rather than drag and drop scriptlets, they would be completely fubard. IF they actually understood structured programming, Plex could be a wonderful piece of database management software. They don’t so it isn’t and never will be anything more than a bug-filled resource hog. (If it takes over a year to debug a program then the coders have no idea what they are doing and the software should be completely removed from public availability until it is debugged COMPLETELY).

As a black hat, I have looked at your sorry excuse for program code and I laughed so hard I had tears in my eyes. Is Plex and example of what a college graduate with a degree in ICS/CIS/CS can do? If so, no wonder we (the USA) are so far behind technologically.