Is there a good reason why we need multiple python processes running even after updates are finished? I’ve looked at various posts advising turning off the auto-updating, etc. This doesn’t seem to resolve matters, however. I still routinely find up to 12 running and taking up a chunk of memory. Why do they not shut themselves down?
Thank you.
I have had this problem in the past. It seems that the latest update for me cured this persistent issue VERY WELL!. I am on Windows 7, Chrome browser at version Plex Media Server 0.9.16.4 - Good luck to you on your coming update
Do either of you have any channels installed? Some of the unsupported community-run channels well spawn their own Python process. It can add up eventually
Plex uses Python to run some of the background processes. Some of these processes must always run, some don’t. You’ll need to provide your PMS log so we can see what is running.
If more processes startup after this, those are mostly due to channels like Vastinator says above. If they don’t shut down, it could be bad coding in the channel, which Plex would have no control over.
Thank you, here are the two latest log files.
After stopping, restarting after a few minutes and not touching it, I only have two Pythons running at present.
Cheers.
Latest two after I came back to the computer to find six Pythons running (with nobody viewing).
Cheers.
I see basic Plex plugins running. You have your library set to do an automatic update every hour. The plugins running are basically the agents and associated bundles needed to perform the update. So everything looks normal. If you don’t want these extra processes running, turn off the automatic update for your libraries.
That doesn’t answer why they don’t shut down after the update.
And actually, I have it set to update when there are changes.
This still needs some looking at.
I don’t have mine set for timed updates any longer. Only for when a change happens.
Python processes are still left behind. They are typically using 0% CPU, disk or network. They just sit there taking up memory.
Cheers.
There are still certain things that need to run in the background for the updates to occur, even when set for only when changes occur. The agents are also typically left to run in the background to be more efficient when they are needed. They could potentially be made to load and unload as needed, but that could be said for anything that runs in a background process. The amount of memory taken up by the agents should be minimal compared to your computer’s overall memory usage.
