Server Keeps Crashing

Plex Media Server Desktops & Laptops
21

@sa2000 Thank you for replying.

Debug logging is enabled. I’ve attached the requested logs in the .zip. I added a log just before causing the crash, and 1 soon afterwards. When causing the problem to happen, I barely see a dent in my memory usage. It always hovers around 4%.

If needed I do have other memory module that I can switch out, if needed, but I don’t think it’s happening due to lack of available memory.

System Specs:
9x 16GB PC3L-1280R [Registered Memory]

x4ql82y96p1e.jpg773×224 83.2 KB

Running PMS 1.13.2.5142

22

@Doramius said:
@sa2000 Thank you for replying.

Debug logging is enabled. I’ve attached the requested logs in the .zip. I added a log just before causing the crash, and 1 soon afterwards. When causing the problem to happen, I barely see a dent in my memory usage. It always hovers around 4%.

If needed I do have other memory module that I can switch out, if needed, but I don’t think it’s happening due to lack of available memory.

System Specs:
9x 16GB PC3L-1280R [Registered Memory]

773×224 83.2 KB

Running PMS 1.13.2.5142

The Plex Media Server.exe process has a max allowed memory of 2Gb - so all this RAM on the system would not help if we are getting close to the 2Gb limit.

It looks like a massive library is causing this. We do have an issue that is currently being fixed to do with the serialization of a JSON response and the use of memory.

There was a long run without any crashes between Jun 10, 2018 02:52:08 and 13:16:16
But then the process kept crashing after that at 13:36:31 and 13:37:07 and 13:37:17 and 13:38:52 and 13:39:32

This shows memory issues soon after launch

Jun 10, 2018 13:36:30.472 [3484] ERROR - Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Jun 10, 2018 13:36:30.472 [3484] ERROR - Error resizing an image, we don't trust what we cached [D:\Plex Media Server\Cache\PhotoTranscoder\f7\f7ce17f783f8f933886b76ed231a8978633a22f6.jpg]

Jun 10, 2018 13:36:30.768 [1728] ERROR - Format [JPEG] - Insufficient memory (case 4)

and all the crashes are arising after accessing one specific large library - the Music library with media in this path I:\Music - I can see successful access to the library when viewing by Artist but crashing when viewed by track

If you enable verbose logging, we can establish which client app / device and if JSON is selected (I suspect it may be - if not, then it would be a different issue from the one that is being fixed at the moment)

Settings / server / general / show advanced and enable verbose + debug logging
and get the logs for the next crash and then disable verbose logging

23

All the crashes follow this request

Jun 10, 2018 13:36:25.244 [0460] DEBUG - Request: [10.0.0.164:57303 (Allowed Network)] GET /library/sections/3/all?type=10&includeRelated=1&includeCollections=1 (10 live) TLS Page 0-11983 GZIP Signed-in Token (Doramius)
Jun 10, 2018 13:36:25.244 [0460] DEBUG - Setting container serialization range to [0, 11983] (total=-1)
Jun 10, 2018 13:36:25.684 [1236] DEBUG - It took 156.250000 ms to retrieve 1 items.
Jun 10, 2018 13:36:25.696 [5448] DEBUG - It took 156.250000 ms to retrieve 41 items.
Jun 10, 2018 13:36:26.328 [0884] DEBUG - It took 156.250000 ms to retrieve 1 items.
Jun 10, 2018 13:36:26.344 [5448] DEBUG - It took 140.625000 ms to retrieve 134 items.
Jun 10, 2018 13:36:26.428 [5448] DEBUG - It took 0.000000 ms to retrieve 134 items.
Jun 10, 2018 13:36:26.640 [6660] DEBUG - It took 93.750000 ms to retrieve 126 items.
Jun 10, 2018 13:36:28.204 [0460] DEBUG - It took 6703.125000 ms to retrieve 11984 items.
Jun 10, 2018 13:36:28.268 [0460] DEBUG - Setting container serialization range to [0, 11983] (total=38396)

serializing 11984 items - what is the plex client app running on 10.0.0.164 ?

The verbose logging would identify it and indicate if it is asking for the response as a JSON

24

@Doramius

The client app behaviour is not right. Should not be asking for all music tracks. Normally requests are paged with say 50 or 100 items at a time for each request

So app and version would be important to know

and the verbose logging should tell us more

Thanks

25

Sorry for the late response. It is a very large library. It contains a lot of my old airchecks and transmissions when I was a broadcaster, along with my regular music library. The 10.0.0.164 is just another computer on the network that I used to access my Plex music library. I’ll run the crash again after I setup the verbose logging.

The system is a server for other applications, but I’ve turned them off to rule them out of causing issues with PMS. I think the system would be a bit overkill for Plex alone. Although, the CPU power has been fantastic for transcoding. :wink:

If it is due to the large library, is there anything I can do to help reduce or bypass the problem? Again, thank you for the help.

26

@Doramius said:
The 10.0.0.164 is just another computer on the network that I used to access my Plex music library.

I need to know what Plex client app it is that you use on this other computer to access your music library and what version of the app

27

I’m pretty sure it’s just the Plex Web app. I’ve used different browsers with the same result, but for the testing I’ve been using Chrome. The web version says 3.55.3

Attached are the verbose logs.

EDIT: My PMS was updated to 1.13.2.5154 before the verbose log was enabled, but the crash still happened.

28

@Doramius said:
I’m pretty sure it’s just the Plex Web app. I’ve used different browsers with the same result, but for the testing I’ve been using Chrome. The web version says 3.55.3

Attached are the verbose logs.

EDIT: My PMS was updated to 1.13.2.5154 before the verbose log was enabled, but the crash still happened.

Thank you. Yes I can see a massive request from plex web at 07:57:22

Do you renember the steps to get the crash - any specific selection / playlist

29

I was just randomly selecting tracks. I could try again and get titles, but it really was random.

30

Will need to reproduce the problem - so any steps that you can give would be of great help , which view / actions. Were you scrolling through a large list

31

@Doramius I have reproduced the issue - thank you. It has been referred to the Plex Web team

32

@Doramius said:

If it is due to the large library, is there anything I can do to help reduce or bypass the problem? Again, thank you for the help.

The problem is now understood. The Multi-Select functionality, I am afraid cannot be used for a massive All Tracks library view. It is a limitation of that feature and was not intended that you would be doing a multi-select whilst on the All Tracks view for a massive 38,000+ music tracks

The feature will be disabled for large libraries. Use smaller items views for multi-select

1 Like
33

Sounds good. At least I know what is causing the issue and can avoid it. Hopefully, it will help others with the same issue. Thank you, you’ve been great.

34

Even better news - latest Plex Media Server beta = version 1.13.4.5251 has a change that reduces memory usage when dealing with requests as was seen here.

See Release Notice Plex Media Server - #224 by emilybersin

  • Shrunk the excessive memory usage when serializing large JSON trees (#8579)

I have tested multi-select with libraries of 13,000+ and 16,000+ music tracks and no crashes. You could try and see if it survives with your library !

35

Hi Guys,

I’m having a similar problem. I had Plex Server running on my old PC, and it worked perfectly. After that PC died, I moved everything over to my laptop, and since then I have had PMS crashing constantly - sometimes as soon as a minute after starting playback. I attached the log files. Any help or advice would be very much appreciated! :slight_smile: Thanks for the great software, aside from the recent problems, it really is fantastic!

Plex Media Server Logs_2018-07-13_12-40-51.zip (2.7 MB)

36

very different - but a crash

You appear to be suffering from one of the many bad dll’s that crash mswsock.dll. In your case it is EasyRedirect.dll

See this support article
https://support.plex.tv/articles/206910047-windows-repeated-crashes-of-plex-media-server/

37

I’ll definitely check it out. I need to clone my current setup first. I have no issues with running beta, but I need to make sure I can go back to the original setup if there’s any stability issues.

This same issue doesn’t happen to video, as well, does it? I don’t have anywhere near that number of movies, but I’d hate to unsuspectingly run into the the issue in one of my video libraries, somewhere in the future.

38

The multi-select functionality is available for videos as well as music as well as photos and the server should now cope with selections from a large set - i have tried it with up to 16000 item library

1 Like
39

Sounds awesome. Thanks. I’ll definitely be checking it out.

40

Thanks for the advice and help sa2000 - I deleted the program and haven’t had an issue since. Great to have Plex working again - thanks so much!