Thank you for sending me the recent deadlock diagnostics from the 14th / 15th February. Perfect set of diagnostics. They show build up of requests soon after launch and eventual Service Unavailable errors (Error 503) start to get returned the following day.
I have referred the diagnostics to our development team
Yes I can see a crash but the crash dmp files did not get uploaded to the crash reporting systems.
Can you zip the whole of C:\Users\Matthew\AppData\Local\Plex Media Server\Crash Reports and send me the zip
@sa2000 The Crash Reports folder is empty. There are a couple folders and some empty files in there.
Have you checked all versions directories ?
@sa2000 Yes, I have directories for versions from 1.10.x through 1.18.x. The only one that has anything in it (other than subdirectories) is a crash from 1.11.3.4803 in July 2018.
That is unfortunate. Does the Application Event Log have entries - (1000 and 1001) for Plex Media Server.exe ? For some crashes like heap corruptions or memory allocation failures, crash reports might not get produced as the process to create them may fail.
All I can suggest is run with the latest release with debug logging and crash reporting enabled and we wait and see what happens after next crash
@jfox21381 - Thanks for all the diagnostics. The cause has been identified and may lead to the server running out of resources after about 22 hours of running under certain circumstances.
A fix has been produced and will make its way through the release process
Thank you for the excellent diagnostics
I have sent you alpha build 1.19.1.2559-68863f99a which has a fix for the issue that may lead to the server locking up after about 20 hours and 503’s returned once the queue size reaches over 4000
A fix for this deadlock has been released in Plex Media Server beta 1.19.1.2589. The deadlock may arise after about 20 hours of running
Release Notice: Plex Media Server - #328 by ahiyahiya
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
