Do you have a flat structure for the media with one folder holding all media or is it structured following our subfolder guidelines ?
eg for TV Shows
Naming and Organizing Your TV Show Files | Plex Support
In this case itās something like ā/Shows/Name/Name s01e01.mp4ā, without a season folder. I have this naming all over this and other libraries and it works without any problems.
There are other episodes in that folder with other video containers that work fine, itās only when i put the FLV one in there that it crashes on scan. It doesnāt even have to have a proper name, ātest2.flvā will also crash it, so will āShow s01e01.flvā
Thanks - could you enable verbose logging in server advanced settings in addition to the LogMemoryUse and send me logs with a scan of the library with that flv file - you can send me the logs zip by private message
thanks
As Iāve already stated, itās only my TV library and only versions after 1.31.0.6654 that have the problem.
Iāve attached a pared down log on 1.31.0.6654 of it successfully adding an entry to the affected series (as usual, I copied a file that was already there and renamed it something else as my ānewā entry). Canāt help you out with logging memory on an affected version at the moment because I canāt think of a way to externally log memory/CPU usage time-stamped down the level youād need to tie it back to actions shown in the Plex log file.
Plex Media Server_success_scan.log (345.8 KB)
Just one more data point. I too have runaway memory of plex process when kicking off a tv show āScan Library Filesā. This is a Windows 10 PC with 7 internal hard drives for data and 4 USB drives for backup. Normally Plex process sits at 50MB memory, but as soon as you kick off the scan, memory climbs to over 12 GB in about 10 seconds, cripling the PC for anything else. Eventually, the process crashes and I can regain control, but sometimes it takes down the PC and it needs a hard reboot. This is the worse it has ever been. I noticed the process was crashed over night (or hung and needed a restart) when the credit scanning was turned on. I turned off all that stuff (credit, intros, chapters thumbnails, all logging) and it still does this. At this point I cannot add any more media to the server due to this issue. Plex has really replaced my SageTV setup for my family but now it has become unreliable. Any help would be appreciated.
After some more debugging, I have many old files that were recorded using SageTV (mpeg .ts files). The logs show it was performing a scan of those files before I killed the process, so I removed those folders from the TV Show Library so NONE of the old SageTV recordings are scanned. Now I donāt get the runaway memory, and the scanner finishes with the analysis and my new files show up. I did a checkdisk on all drives, so that should not be a problem, but maybe some file is bad. I will put back each of the 3 folders, one at a time to see if I find a pattern. I hope this helps someone seeing similar memory issues.
Thank You @hornms - that would be good if you can track it down to a certain set of files or file naming / folder structure and would love some server logs with the LogMemoryUse server setting set to 1 and recursive directory list with /s for the TV library location paths
SageTV files seem to be pop up on the memory usage issue by a number of users - a few here as well in this forum topic Plex Server (Windows) crashes after version 1.3.1.0.6654 - #43 by robertsig
Would like to know if the others in this thread having memory issues also have files from sageTV recordings
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
1 Like
Looks like my issue was in fact that file naming bug. Somehow one of my episodes had gotten named āSouth Park - S18E07-16779735 - Grounded Vindaloop.mkvā, which was the only file not in the format of āSouth Park - S##E## - Episode Titleā in that directory (i.e. the only one that vaguely looked multi-episode). Removed those extra numbers from the file name, upgraded Plex to 1.31.2.6810, scanned my TV show library, runaway memory usage did not occur.
Exactly - the problem came in when we allowed the non-standard Sonos syntax
- (Scanner) Adds support for the Extend multi-episode format i.e. S01E01-02 (#14064)
A fix has been produced and will get released very soon
The new beta with the fix has now been release - PMS 1.31.3.6868
- (Scanner) Certain episode filenames could lead to excessive memory usage (#14215)
THANK YOU PLEX! With fix #14215, I can now add back my SageTV folders and the scanner no longer has the runaway memory issue. Meta data is properly scanned and the tv shows are back in my list. Unfortunately, they are now listed as the most recently added, but at least they are back. Good work by your team and thanks for the fast release!
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
