Server Version#: 1.23.0.4438
Player Version#: n/a
Plex Media Server Logs_2021-04-30_12-38-59.zip (2.1 MB)
Well this can’t be right, can it?
For the last week I’ve been having random lock-ups on my server, requiring a full restart to recover from. But having done some further research it appears to be Plex Media Scanner going haywire while analyzing loudness (of, I assume, music as I had just added some new music this morning when this lock-up occured.)
It’s getting hard not to take the complete lack of interest in any issue I post personally. Not one of the issues I’ve raised recently has received even a nod from a “Plex Employee”.
I guess I’ll turn off the volume normalisation and that’ll be another thing in Plex that just doesn’t work (for me) but no-one cares enough even pretend to look for a solution.
Wait - you have 48GB of RAM? 48 Gigs?!? That’s quite a lot, which makes me kind of understand that you miss all of that. I’m fine with the 8GB that I have, but also, I’m not hoarding TBs of music to analyze (and even if I would, I would need to spend another $120 to get a license/Plex Pass to analyze for volume). But that is indeed abnormal, no software should be using that much RAM (unless it’s the type of software which does - and the Plex Media Scanner most certainly is not of that type). You might want to have a PlexDev take a look at your specific problem 
You’re using a dual-socket system?
In your logs, it says:
Apr 30, 2021 12:18:10.555 [0x7fb0cfc01b38] ERROR - Analysis: Format error 'Invalid data found when processing input'.
about 12 thousand times in 20ms. But that shouldn’t make your server use up that much RAM…
Kind of what I’m hoping would have happened posting here, on the Plex forums…
It’s a single processor, but yes, it’s 16 cores, 32 threads, 48GB - it really shouldn’t be choking on anything Plex is trying to do. As you pointed out in your second post - there’s definitely an issue, and it might even be an issue with a specific file I’ve added to my system (and how would I get Plex to tell me which file, I wonder - that’s not in the logs…) but Plex shouldn’t immediately fill 5 log files with the same message, eat 48GB of RAM (and (8GB of Swap), ■■■■ the bed and take down my entire server… Ever. No matter how much garbage I feed it.
Well, now we’ve got the weekend and the Bank Holiday out of the way, I wonder if there are any Plex Staff prepared to even acknowledge that this isn’t normal behaviour and to help guide me towards ascertaining what may be causing it and how to solve it? Maybe? Bueller? Bueller? Bueller?
So this is it then? This is the thing that makes me move to a different media server standard, after many many years of being a Plex “Lifetime” Support (and advocate, I may add). I literally cannot fathom how not one single person can offer even the smallest bit of advice here. I cannot comprehend how no dev, or support agent, or team-member, or whatever at Plex hasn’t happened past this post and thought “This must be really frustrating for the guy; maybe I’ll just drop a ‘Yeah, this doesn’t look right but can you …?’ to give him an iota of direction here”. Nothing. Not a thing. Not. A. Thing.
Solved in this thread.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
