I will definitely do that. I was pretty sure this last time I had this fixed as I got nearly a week in without issues until today 
Thanks!
Awesome, hopefully with more cases popping up it will help the team get to the bottom of it, and kill this bug 
No logs to send as I’m short on time but I can report I found how to replicate the issue. I use Overseerr to handle requests for users. Overseer does a full library scan in Plex every 24 hrs. I can also manually initiate a scan. When I manually initiate a scan, after a minute or two, Plex will deadlock. Once I stop my Overseerr docker and kill Plex process and restart it, Plex comes back up and functions. I have tested this multiple times and EVERY time, Plex deadlocks when a manual scan is ran. Talking to @morpheus2n2 , I’m going to assume Petio causes the same behavior as it scans every day at midnight. This explains why my server deadlocks overnight as every night the library scan kicks off.
1 Like
@sa2000 Ok I got up to Version 1.22.0.4157 and it has just done it!!
Diagnostics have been grabbed and sent
Thanks - these 1.22.0.4157-d1699ac4a diagnostics have been passed to the devs. We now need to establish if 1.22.0.4145-0af3a4016 has the problem
Last night Plex seemed to have crashed and went into full deadlock, wasn’t even able to via the connections page via http://127.0.0.1:32400/connections?X-Plex-Token=########
However when I looked at the log file I found this absolutely every where from about 3:17am right up to the crash at 5am “Thread: Couldn’t add a new thread to the pool of size 0: boost::thread_resource_error: Resource temporarily unavailable”
This is the first time I have ever seen that in the logs any ideas?
Its worth noting I am running an older build as per the request here Plex Deadlocking with to many hung connections issues for last 4 months. (This ended up giving me anxiety attacks!) (Edited title for clarification) - Plex Media Server / Desktops & Laptops - Plex Forum
so this is probably something that’s been fixed or it may not have.
1 Like
@sa2000 Other than the crash/deadlock listed above (which I don’t think is the same problem but im not an expert lol) Build .4145 has been running perfectly fine for a almost a week now.
So I am confident that this build is free of the issue and .4157 is where it starts.
1 Like
Hey man - I just want to say I’m thankful you’ve put the time in bisect this. 
1 Like
Thanks for all the tests - the issue with 1.22.0.4145 was memory allocation error but no deadlocks
So it appears the deadlocks came in between these 2 public releases 1.21.4.4079 and 1.22.0.4163
and between these 2 beta releases 1.22.0.4145 and 1.22.0.4157
This has been fed back to the development team
No worries, I have installed latest Beta as asked and will keep eye on it, and if the Deadlocking returns I will make sure to pull all the diagnostics for the team as per the norm
Thank you so so much for all the support on this and I am pleased that the info @kegbeach and I have sent is proving to be helpful for the Team
I had 1.23.4.4775-b7e0c30f2 running for about 36 hours before it did it again.
Diagnostics captured and PM’ed
I have also downgraded back to PlexMediaServer-1.22.0.4145-0af3a4016 as asked
Has there been any update from the team? Really curious as to if they have any ideas or still very stumped lol
@kegbeach @AHickle @JDA88 @jj666 Are you guys still getting this?
I’m curious as its approaching 6 months now for me and Im having to run a build from 6 months ago that has yet to have this issue (I get get other issues that have been fixed in builds since 
) lol
Yea, 4775 happened once so far.
4K? Wow, mines never got that high, have you been pulling the diagnostics and sending them along cos that defo needs looking at
No, the server version ends in 4775. The latest one.
Pmsl Yeah happened to me once when I moved to 4775 and then I dropped back down to 1.22.0.4145 as its the last stable build I used before all this lol.
You have been grabbing diagnostics though cos I am hoping they are close to finding the course
Do you use Live TV & DVR? The server I use for that is the only one experiencing the problem. It’s also the Docker container version.
Nope
@sa2000 I’m not holding out any hope but I have moved to build 1.23.4.4805 today as its just come out to see.
Just to recap, I moved to Build 1.23.4.4755 Last Tuesday as requested and it Deadlocked after 11ish Hours (Relevant Diagnostics all sent) So I then Moved back down to 1.22.0.4145 witch other then the GPU Memory bug that has been fixed in later builds this has run for better part of 3 weeks (other than when I switch build for testing then had to downgrade back) with no issues at all.
So with todays release of a new Beta build I am trying again on the just in case but I am not holding out much hope with this build either!
1 Like
Do you have your server exposed to the outside internet for remote viewing or is it isolated to the LAN?
