The fix for the massive DB and very large number of Extras leading to memory allocation failures and crashes is now out in Plex Media Server beta 1.25.4.5426
See release notice
(Metadata) Some users could end up with massive amounts of duplicate extras (#13241)
The immediate issue of crashes, memory allocation failures get resolved on first launch. The database will shrink slowly over a number of weeks. For example if there are a million extras on a movie - it would take about 11 week to purge all the orphaned database items after the initial deletion of the extras - the purge is up to 100K at a time when the database is optimized and the scheduled task runs this once a week. Of course users can run manual database optimizes which would reduce the period. Note that during an optimize the server is effectively locked out and it may initially take 20 minutes or more
Anyone with the early alpha build with the initial fix should update to this beta
Thanks to everyone for help in tracking down this bug with investigations and diagnostics from @shayanzadeh@Volts@jakehoms@spartan018 - just to mention a few
I’ve updated to version Plex Media Server beta 1.25.4.5426 and I’m still crashing from memory issues (using way too much ram) during scheduled tasks and am looking for help options for a fix. Will optimizing my database frequently/often help accelerate a fix for this issue for me? I’ve tried setting Plex to not send crash reports so that I can send them, but that setting appears to get reset with every restart I have to do with Plex, so I don’t have any crash reports to upload here. I do have my logs from my most recent crash put up in the thread I had started about my issue months ago here: https://forums.plex.tv/t/server-frequently-crashes-even-after-latest-update/761650/30
So, I’ve been optimizing all day in the background the past couple days, and the size of my database hasn’t changed and I’m still crashing during scheduled tasks
Please ensure debug logging is enabled on the server and when the problem arises download the server logs immediately after restarting the server and post here so that an investigation can be started
I have been monitoring this and several other topics on the mater of crashing. I have 2 dedicated Syno NAS devices with more then enough RAM (16GB), but since version 1.23+ at some point, I keep getting random crashes. Sometimes even when the server is not even used.
I have set up 4AM local time a scheduled restarts of Plex server, but this does not mean that the server will not crash the same day or sometimes after several days.
I have just had a crash, and started the server up again. Fresh logs are attached.
This happens on both server as they run the same PMS version and are on the same CPU arch.
I found some uploaded crash reports - could you get me more up to date debug server logs to see if they would match the recently uploaded crash reports
and try latest beta to see if the situation changes - current beta 1.25.6.5577-c8bd13540
Atm I am on 1.25.6.5545, still haven’t update to 5577 as for the past 7 days I haven’t had a crash on either of the platforms until yesterday, when one of the servers crashed.
Adding its logs now. I will test the new version this weekend.