PlexScriptHost.exe

I could provide the logs but the last time I did that absolutely nothing came of it. Since I don’t know what is collected by the logs and can only read what isn’t encrypted for lack of a better term, why should I submit them again? The simplest solution is to simply uninstall Plex and hope that someday it will be written far better with the ability to make changes without a bunch of forced presets. I already wrote my own program to access the movies remotely and mine doesn’t try to kill my CPU or use all the resources because of multiple instances of a program that actually causes another (conhost.exe) to run just as many instances. The problem is that programmers these days are never taught properly structured programming which is what leads to a lot of the issues in most software available these days. Why does PlexScriptHost.exe have to open so many instances and command prompts? There is no logical reason for that or for using Python. I guess being involved in the IT field since before PC’s were even thought about and learning things like assembler are why I get so frustrated with the way software is so poorly coded these days. Now excuse me while I uninstall Plex. Again.

There are several aspects here :

  • the general point you refer to about the programming and whether it is right or wrong to have up to 10 x PlexScriptHost.exe processes and corresponding conhost.exe processes on launching Plex Media Server
  • specific points re cpu hogging processes taking a lot of cpu

On my systems the 10 x PlexScriptHost.exe processes do eventually reduce back to just 2 or 4 processes. It may take a few hours for them to wind down but they do. The processes are for each of the core bundles and there is a cap of 10 on windows and if one needs to start - an idle one is shutdown to make room.

As far as i can see these processes do not actually consume much CPU and are idle most of the time

If these processes are consuming a lot of CPU on your system all the time then we need to go down the track of identifying from logs what is happening and which of the bundles are implicated.

we may find that the logs do not show any activity but CPU is being consumed and this may lead us with use of further diagnostics - eg SysInternals Process Monitor to the yet to be resolved previously seen issue of a loop of some sort after a tcp disconnection on 127.0.0.1 for a PlexScriptHost.exe process. This was last seen here https://forums.plex.tv/discussion/154069/constant-network-changed-and-50-cpu/p3 and having more evidence of it still occurring should help in giving this specific problem some priority - but we have not reached this point in investigating your problem

I am seeing this issue as well, and the performance of my machine has degraded. I continually get “We’re unable to play this video, make sure the server is running and has access to this video” on my Roku, and it’s continually buffering. I never had these issues until the recent server updates. My machine is very capable, and the only thing it does is run Plex and Windows Media Center, so it just sits idle most of the time.

@cmarcho said:
I am seeing this issue as well, and the performance of my machine has degraded. I continually get “We’re unable to play this video, make sure the server is running and has access to this video” on my Roku, and it’s continually buffering. I never had these issues until the recent server updates. My machine is very capable, and the only thing it does is run Plex and Windows Media Center, so it just sits idle most of the time.

One should investigate starting with is giving rise to We're unable to play this video,..... error and if it leads to PlexScriptHost.exe CPU usage problem then fine - but suggest you raise a separate a forum topic and provide screenshots/time of error and debug Plex Media Server.log covering the time and if you believe it is python related - also the PMS Plugin Logs folder log files.

See Reporting issues with Plex Media Server which advises on doing controlled test with debug logging and restarting the server before doing the test to reproduce the error and get diagnostics

I’m also having the problems stated here. I’m currently too busy to debug anything and I don’t see any logs. Multiple exes in task manager.

@ReFLeX135 said:
I’m also having the problems stated here. I’m currently too busy to debug anything and I don’t see any logs. Multiple exes in task manager.

It is normal that there are multiple PlexScriptHost.exe processes in Task Manager initially. These should be idle after initial period and also come down in number after a while.

It is only an issue if the processes are permanently clocking a lot of CPU use and that would be when debug logs are needed to investigate why it is happening.

I am experiencing this with Version 0.9.15.3

Seems it only happens when I reboot the computer and the process starts with windows. My workaround is to exit plex media server and start it again. I think it’s a stupid bug - but should get fixed. Yeah yeah, its pretty harmless and there is a way around it, but its unnecessary. Don’t just backlog and ignore it

wow, an ongoing problem that obviously has not been properly defined or solved yet. What a shame.

@jesserooney said:
I am experiencing this with Version 0.9.15.3

Seems it only happens when I reboot the computer and the process starts with windows. My workaround is to exit plex media server and start it again. I think it’s a stupid bug - but should get fixed. Yeah yeah, its pretty harmless and there is a way around it, but its unnecessary. Don’t just backlog and ignore it

@jimmolinaro said:
wow, an ongoing problem that obviously has not been properly defined or solved yet. What a shame.

If you are experiencing this issue, please provide your server logs after restarting PMS. Make sure all processes have shut down before restarting PMS. That is the only way to know what is going on. Stray processes could be due to not shutting down properly previously, or other channels/plugins not working properly. But without the server log, it is hard to determine the problem.

@jesserooney said:
I am experiencing this with Version 0.9.15.3

Seems it only happens when I reboot the computer and the process starts with windows. My workaround is to exit plex media server and start it again. I think it’s a stupid bug - but should get fixed. Yeah yeah, its pretty harmless and there is a way around it, but its unnecessary. Don’t just backlog and ignore it

I am trying this workaround and it seems that it might be working for now. I will monitor and report my results.

After a couple recent PLEX Windows server upgrades and the big Roku PLEX app upgrade where now you can see your TV show background when fast forwarding or rewinding in the PLEX Roku app I’m having the same problem with constant buffering in PLEX and Roku, starts happening as soon as I start to fast forward or rewind my video until I get the We’re unable to play this video,… error. I noticed the multiple PlexScriptHost.exe process running in Task Manager (4) and a search brought me here. I’ll try this workaround again but i think I’ve tried it and it hasn’t helped. Before these upgrades PLEX was rock solid on my Roku 3.

@PLEX_EBB said:
After a couple recent PLEX Windows server upgrades and the big Roku PLEX app upgrade where now you can see your TV show background when fast forwarding or rewinding in the PLEX Roku app I’m having the same problem with constant buffering in PLEX and Roku, starts happening as soon as I start to fast forward or rewind my video until I get the We’re unable to play this video,… error. I noticed the multiple PlexScriptHost.exe process running in Task Manager (4) and a search brought me here. I’ll try this workaround again but i think I’ve tried it and it hasn’t helped. Before these upgrades PLEX was rock solid on my Roku 3.

You would be better off raising a new topic or reading support pages and forum topics relating to buffering. Having 4 PlexScriptHost.exe processes should be harmless unless they were clocking up 100% CPU of each processor
See Why is my video stream buffering

Yep… got nothing out of this thread. Definitely still an issue…

1 Like