…uhhhh, everything here is saying it’s an MP3 file.
Well, except for it apparently not showing up in Plex itself.
I’ll see about a new topic. Meanwhile, I’ll pull that file and its brother out of the directory and see if that changes anything.
well 17 replies of offtopic nice.
The comments were originally related as he was experiencing the same issue. Turns out it may have been due to the file he had. I was trying not to get off topic by discussing the file itself.
I’ve also started having 100% CPU usage since upgrading to Windows 10 version 1809… I don’t have Windscribe VPN loaded either as I though that was the issue (and it was a while back but they were kind enough to add an option not to kill open TCP connections and Plex has a bug in that it freaks out when that happens that has not been fixed)… this new issue might also be related but perhaps to Windows 10 this time or some other process on my system I’m trying to work out what (but it would be really nice if Plex was able to fix the core component that is so temperamental it seems)
I’ve pretty much given up on this issue as it’s entirely random at this point.
Yes… If nobody from Plex pickes up, we are food for the lions.
We are here to help. If you are experiencing this, please grab the PMS logs while this is occurring or shortly after and let us know what time you noticed this activity.
And here we go again, though I’m mindful of what happened previously. I just caught PMS pegging the needle again, so stressing the CPU that the entire computer ground to a complete halt until I exited Plex after grabbing the logs. This started around, ummm, I’d say a bit after 8pm AZ time, Plex was in Random Album Mode, and had landed on a directory with rips of a Wailers single, “Guajuara Ska” – mostly played them one after another, no blips, but I was watching a performance monitor and BLAMMO.
Dell Optiplex 760, 8Gb, PMS 1.14.1.5487, playing to the current Roku client. Logs attached, and I’ll send a link to the files via PM so we don’t get to going back and forth about those here.
1 Like
Yes. Still a problem. But it has nothing to do with what you are doing with Plex at that moment. I don’t add new movies, and also when just restarted the computer it happens. Didn’t touch Plex.
Looks like it has to do with your audiobooks library. You have Plex set to update your library when a change is noticed. Were you actively working on these at the time. From some of the folder names I saw, it appears that you use this folder as your working directory when you are doing stuff with your audiobooks. This is unadvisable with the automatic update setting. Try chaning how you store your audio books so that only finished ones are in Plex. Or disable the automatic update setting.
I don’t have any audiobooks or photos here. But it could be an extra cause.
That’s the thing, though…I wasn’t adding audiobooks, but had removed a group (new rips live on one server until I burn backups to DVD, then I move them to the other server – in this case I moved them to a new directory that hadn’t been set up as part of the audiobooks library on Bearcub.)
I’m really not sure why Plex should be thrashing the CPU on media removal. I understand it tends to go nuts on mass media additions as Bearcub’s iteration of PMS will crash altogether if I do a large set of moves (hence the new directory; I can then drop everything into the target directory at once.)
I’ll try disabling the automatic setting on Brain; I certainly should have done that on Bearcub by now, which is my error – I’ll make the switch as soon as I send this, and go to doing either manually triggered updates, or just the nightly scan while I’m asleep.
So, basically nothing related to the music files I put up? I didn’t think it was, but given that you and I have demonstrated that I’ve ended up with some really odd media files in the past, I wasn’t taking chances.
i dont have audiobooks or photos either.
this bug caused to my microprocessor die. a week ago i found when woke up that my processor was at 90º running 100% cpu usage from plex scripts process for a lot of hours. the pc was clunky so I restarted it and never turn on again. not even the bios. after a few days of checking the cpu was fried.
Changed the cpu and I here again. Cant understand how a bug so important like this happen and is not fixed.
removed my plex suscription, all updates are about @#~€% tv tuner that cant even turn off the services…
plex is not the same… not going to pay for not fixing important bugs.
Since these are audiobooks, it could be that Plex is trying to match these files to a regular music album. I couldn’t tell how your library was set up from the log, but I would suggest checking and making sure the agent is set to “Personal Media Artist”. This way Plex won’t waste any energy trying to match them. If you did not set this agent to begin with, then unfortunately, it won’t change the agent already used for whatever you already have, it only affects new content. If this is the case I wold suggest recreating your audiobook library using the personal agent.
Sorry that this happened. However, if your computer dies from running at 100%, that could indicate a physical problem with your system. A computer should not have problems running at 100% load for an extended time if the system is working properly. I would definitely check your cooling system before this happens again.
If you happen to have the Plex logs from when this happened, I’d be happy to lake a look.
i already shared logs. if there’s nothing then i cant help you. this happen randomly. today happened again.
and that excuse of running 100% shouldnt be a problem, i know, my previous silicon lotery was not good and my previuos processor was a bit hot than normal. but that shouldnt die in 3 years if was not for this ■■■■■■ bug that use 100% of your cpu for hours and hours ultil you find out in the task manager…
i imagine all the others users that experience this and never find out that there is scripts using all the cpu for hours.
i did a full reinstall from 0, disabled all tasks, removed all plugins and this still happen. randomly this ■■■■■■ scripts starts using 100% of your cpu. so the problem are in the core of plex. im considering switching my library to another problem, this is getting frustrating and expensive.
You had debug logging turned off previously. I told you to turn it on and leave it on and get me new logs when this happened again. Your old logs don’t help. I need new logs with the debugging info.
I’ll give that some thought. The library for new rips is currently close to emptying out, so it might be worth just deleting and redoing it.
What might be even more useful, though, is to have a library category specifically for audiobooks. It’s extremely annoying to have them always coming up in the new music feed, and as a music category when they’re most certainly not. Same thing with radio shows and podcasts – why is there no option to create a podcasts library when podcatching is now built into the damned server?!
That last part is something to take to another topic, though.
I hope that when the CPU was replaced, the CPU cooling fan was replaced as well. Having the fan seize up for whatever reason, or the thermal paste fail, will cook off your CPU in no time.
When Plex maxes my CPU for an extended period, all that usually happens is that the computer turns temporarily into a brick.
there is no cooling problem. the old cpu only had a bad themal (thanks to silicon lottery). i have a h115i corsair watercooling. cooling is not the problem. only a cpu with bad thermal and this ■■■■■■ bug give them the final stab with years of bugging at 100% usage for hours. i already have a new cpu with better thermals, but this not fix the issue with plex.
thats why mining rigs die quickly. is not normal use 100% usage 24/7. stop changing the subject of the bug.
the log is fine, there is nothing in the logs. is was not turned off. what part of “this happen random” did you guys not understand? i dont know when it start, the only time that happen when actually playing a movie i shared full logs with exact time and nothing show up. i even check logs when this ■■■■■■ bug happen AND NOTHING SHOW UP.
so you need to check if your “plexhostscripts” process are not responding and close them is so hard? you add ■■■■■■ process for turner THAT NO ONE USE and you cant disable, but you cant detect having own process at 100%.
and not music or podcast related, I DONT HAVE ANY, and podcast IS DISABLED.
im a bit tired of the excuses. that why i ended my subscription.
