Could you now add verbose logging on the server and get me logs after repeating the sequence before - there was a library scan of the TV Shows library when the crash occurred
Would like to see the logs with both the LogMemoryUse and verbose logging enabled - verbose logging can be enabled through Plex Web server settings with show advanced
thank you
Itās a directory in a 1 TB SSD that Iāve used for recording OTA TV. Most if not all of those recordings were made under SageTV so most of them are in .TS containers but some of them I converted to .MKV.
The few, the proudā¦ Iām a SageTV user as well. Same server with all the tuners and USB-UIRT, etc. It means we need to be more careful than the average bear.
sageTV appears to be mentioned by a number of users - see also this thread post PMS causes 100% RAM usage when any episode added to one specific series - #25 by hornms - I wonder if the naming convention or directory structure has a bearing on the issue
Anyone else with these memory usage related issue also has sageTV files ?
we found the problem - it was due to some specific file naming and recent change to allow for merged episodes where users have multiple sequential episodes in one file
A fix is being worked on
Excellent, looking forward to it.
Think I have been experiencing the same thing, my server will crash at random over night since the last update 
The new beta has now been release - PMS 1.31.3.6868
I suggest you update to the beta which has a fix for the crashes caused by excessive memory usage. If your problem is different and the crashes continue, please provide debug server logs captured soon after a crash and if you can, also look for any .dmp files within %TEMP% (windows) $TMPDIR (other platforms) created at the time of the crash and zip and send to me by Private Message
Iāll give it a shot, thanks
I attempted the same scenario that was crashing it before and so far Iām 5 hours in and It has not crashed.
SageTV FTW! 
Well, at least as long as Comcast supports my cablecard.
Iām hoping that since Plex is an active product it will get ATSC 3 support. I think that will be more challenging for the community members supporting SageTV. My wife still prefers the layout that we had in Sage that showed upcoming recordings, recent recordings and a list view.
Plex doesnāt seem to have that option except when using the webui
There are legal matters to be addressed. See related topic ATSC3.0 Broadcast and AC-4 Sound
I believe there is a legal requirement for broadcasters to continue to offer non ATSC3 channels as well
My understanding is they have to keep ATSC 1.0 channels for at least 5 years after they start broadcasting 3.0
That would mean that in my area they are only required to keep broadcasting ATSC 1 for 4 more years. Hoping Plex will support it by then or Iāll be moving to one of the DVRās that already supports it.
I appreciate your help in getting things fixed with the filename issue.
Ok it seems I have had an old bug rear itās head again.
This here is what has started happening again.
Plex Deadlocking with to many hung connections issues for last 5 months Now!. (This ended up giving me anxiety attacks!) (Edited title for clarification)
Right now as I right this I canāt pull logs or debug etc as Iām at work for next 8 hours but the server has just gone down with 200 connections currently open 
.
Biggest problem is it took a year to get it fixed and gave me anxiety attacks!!
That is bad news. Lets hope we can get to the cause fairly swiftly and have it fixed.
I have responded to your new forum topic on this here Old deadlock bug has reappeared in the last 2 public builds - #2 by sa2000
So far it looks like the latest version doesnāt crash on me.
I take that back. My Plex server froze (crashed) last night. It was version 1.32.1.6893. So Iām now back to 1.3.1.0.6654 and ignoring all update prompts.
Any news on a fix?
The specific memory usage related crashes due to naming convention used by SageTV were resolved and the fix was first out in Plex Media Server 1.31.3.6868 on March 27th and the fix was confirmed by other users
I do not have any logs from your crashes to investigate
I would need debug server logs captured soon after a crash to investigate. If it turns to be a hang as opposed to a crash then there would be need for additional diagnostics.
Hi Guys,
read this issue and have been having āRandom Windows Restart issuesā for week (or is it months?) now. Was searching for a hardware issue because i couldnāt seem to find anything in the windows log which could point me in the right direction. Till i once saw the plex transcoder āeatā all my cpu resources and i decided to downgrade PMS to version 1.30.0.6486. Why this versionā¦no ideaā¦just a lucky guess i guess because i have no āRandom Windows Restart issuesā anymore. Iāll try to install the latest version again and see if it crashes again and if so iāll disable the intro and credit scanning to see if it disappears again. Iāll try to post the logs if it crashes again.
Hope all is not necessary because its already fixed 
