Plex Media Server Crashes Every night

With crash reporting disabled (as you have), I would expect the dmp files to remain in those folders

It is possible that the Plex Media Server process did not crash but hung - that would have been at Jan 13, 2023 03:54
and then the server was relaunched at Jan 13, 2023 07:09

Do you recall if you checked Activity Monitor to see if the Plex Media Server was running or had exited ?

Other locations to check for Plex related crash / diagnostic reports

~/Library/Logs/CrashReporter/
~/Library/Logs/DiagnosticReports/

If the Plex Media Server process is hanging (still showing in Activity Monitor) rather than crashing, then we would need to force a coredump of the process and have zip of that together with the zipped debug server logs

I am afraid getting a coredump is not straightforward - i will outline how it can be done below

In a terminal session, type in command

sudo ulimit -c unlimited

codesign the application to allow lldb to attach to the process.
In Terminal session, type in
codesign -s - -f "/Applications/Plex Media Server.app/Contents/MacOS/Plex Media Server"

Relaunch Plex Media Server

Test out the process for capture of process core dump

For the process dump, Find the PID for the Plex Media Server process from Activity Monitor

In terminal session, type in

lldb --attach-pid <PID>
where is the pid number of the process,
e.g. if the PID for Plex Media Server was 593, type in
lldb --attach -pid 593

This will download and install developer tools and will require confirmation
Once developer tools are installed, repeat this
lldb --attach-pid <PID>
and in lldb, type in
process save-core pmstestdump1

Wait for all the saves to complete and the lldb prompt to come back
Then type
exit

This should have created a coredump file named pmstestdump1 in the current directory in the terminal session

So this proves the process
Restart Plex Media Server now and wait for the hang / server inaccessible

when it happens, confirm it is hung, find the PID number and go through the lldb steps and save the dump to file eg pmsdump1 or pmsdump2 etc

Please zip together with the Plex Media Server logs zip

If the binary files change - eg upgrade to PMS, then repeat the codesign steps

Thank you

Thank you - I have DM’d you with my logs.

Thanks for the logs

There is evidence of a crash at Jan 24, 2023 21:57:10 but no indication that a crash report was created by the Plex Media Server crash detection.

At the time of the crash Plex Media Server was testing out hardware transcoding capabilities

Can you tell me if you are running Plex Media Server as a Service or Scheduled Task ? There were issues seen that may give rise to crashes if hardware transcoding is enabled and the Plex Media Server is run as service

Could you see if windows captured a dmp file into directory
C:\Users\damon\AppData\Local\CrashDumps

There is a registry change that can be made to get windows create dmp files in event of application failures - dumps would then be saved into this directory

See the regedit outlined on this support article Crash Logs: Plex Media Server | Plex Support

You may need to create the directoryCrashDumps - under C:\Users\damon\AppData\Local\

Restart the PC after doing this regedit and creating the directory and then lets wait for the next crash and get the debug server logs after restarting Plex Media Server following a crash and also look for any dmp file within C:\Users\damon\AppData\Local\CrashDumps - zip and upload somewhere and send me link by PM

Thanks

Thank you very much. I’ve enabled the reg key and will send through files the next time it crashes. It’s been stable since the last crash.

I don’t run it as a service, it starts up once I log in. I do run my server as a headless server (there is no monitor plugged into it). So often after a reboot I’ll RDP to it and log in (sometimes I will use VNC instead of RDP).

There would be issues with codecs and hardware transcoding in when running without a display and crashes have been encountered by users. I think some users added a dummy usb device Dummy Plug Virtual Monitor Display Emulator, Headless Display Adapter to get round the issue

A dump with debug server logs would confirm if it is the same issue

Try to disable hardware transcoding to see if the crashes stop

There are two settings in the Server Transcoder (advanced settings)

  • Use hardware acceleration when available
  • Use hardware-accelerated video encoding

Try first just disabling the second setting Use hardware-accelerated video encoding and if that does not stop the crashes - disable the first setting as well and see what the outcome is

Hey @sa2000 I had to wait for Plex to crash again as the file you requested was gone and the directory was full of .dmp files. Attached is the only .dmp after the latest crash.
E1A3DBAF-3B4C-4610-89D2-D20F91E4B4CA.dmp.zip (40.4 KB)

In case the new dump is different - do you have the corresponding server logs ? for the time of the crash - i will look into the dump Thursday or Friday

I hope they didn’t get overwritten. I’ve since opened Plex and began watching a movie. Thanks again!
Plex Media Server Logs_2023-02-01_19-25-26.zip (4.8 MB)

Thanks - yes logs cover the time of the crash (Jan 31, 2023 20:55:24) - I have referred the crash to the development team - how often is it happening? Logs show the previous crash on 26th January

It’s truly intermittent. Sometimes its a couple times a day, then maybe several days then daily…

Plex logs and CrashDump.zip (10.4 MB)

Hi @sa2000 , it’s been pretty stable for the last week or two, but had another crash tonight. I’ve attached the server logs and the crashdump.

Thanks!

Thanks

Looks like may be the system ran out of resources

The crash happened after running for almost 4 days - crashing at 22:00:55 on 10th Feb
Logs actually show problems started at 16:10 - six hours before eventually crashing

At 16:10:07 - there is indication of network dns lookups started to fail

Feb 10, 2023 16:10:07.438 [15116] WARN - [HttpClient/HCl#3b1b] HTTP error requesting GET https://plex.tv/api/v2/server/access_tokens?auth_token=xxxxxxxxxxxxxxxxxxxx (6, Couldn't resolve host name) (getaddrinfo() thread failed to start

After that PMS was unable to add any threads

Feb 10, 2023 16:10:07.438 [15116] ERROR - [HttpClient] Thread: Couldn't add a new thread to the pool of size 0: boost::thread_resource_error: Resource temporarily unavailable
Feb 10, 2023 16:10:08.729 [15012] ERROR - Thread: Couldn't add a new thread to the pool of size 5: boost::thread_resource_error: Resource temporarily unavailable
Feb 10, 2023 16:10:11.036 [15012] ERROR - Thread: Couldn't add a new thread to the pool of size 5: boost::thread_resource_error: Resource temporarily unavailable
Feb 10, 2023 16:10:14.806 [15012] ERROR - Thread: Couldn't add a new thread to the pool of size 5: boost::thread_resource_error: Resource temporarily unavailable
Feb 10, 2023 16:10:18.736 [15012] ERROR - Thread: Couldn't add a new thread to the pool of size 5: boost::thread_resource_error: Resource temporarily unavailable
Feb 10, 2023 16:10:21.049 [15012] ERROR - Thread: Couldn't add a new thread to the pool of size 5: boost::thread_resource_error: Resource temporarily unavailable

This continued until eventual crash

Could be useful to get export of the Windows and Application Event Logs for that day to see if there are any logged system issues on that day

You could save the Application and System event logs in Event Viewer and send me by PM zip of the evtx files

For future crashes, could you enable memory usage logging in PMS - see LogMemoryUse setting mentioned here Advanced, Hidden Server Settings | Plex Support

Further to my earlier response, I can actually see memory allocation errors before the time I mentioned

All the memory allocation errors

Feb 09, 2023 16:49:36.647 [12956] ERROR - [Req#e32ac] Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 09, 2023 16:49:36.668 [25736] ERROR - [Req#e32cf] Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 09, 2023 17:39:39.211 [24764] ERROR - [Req#e565d] Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 09, 2023 17:39:39.263 [6876] ERROR - [Req#e5662] Format [JPEG] - Insufficient memory (case 4)
Feb 09, 2023 17:39:39.321 [6876] ERROR - [Req#e5661] Format [JPEG] - Insufficient memory (case 4)
Feb 09, 2023 17:39:39.340 [24764] ERROR - [Req#e565c] Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 09, 2023 17:39:45.142 [24764] ERROR - [Req#e566a] Format [JPEG] - Insufficient memory (case 4)
Feb 09, 2023 17:39:45.155 [21188] ERROR - [Req#e567c] Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 09, 2023 17:39:45.255 [21188] ERROR - [Req#e56c0] Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 09, 2023 17:40:00.370 [24860] ERROR - [Req#e56c2] Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 09, 2023 17:40:00.613 [24860] ERROR - [Req#e5701] Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 09, 2023 17:40:00.707 [24860] ERROR - [Req#e5704] Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 09, 2023 17:40:02.498 [21188] ERROR - [Req#e5714] Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 09, 2023 17:40:03.231 [17336] ERROR - [Req#e5718] Format [JPEG] - Insufficient memory (case 4)
Feb 09, 2023 17:40:03.493 [24860] ERROR - [Req#e571c] Format [JPEG] - Insufficient memory (case 4)
Feb 09, 2023 17:40:24.861 [24860] ERROR - [Req#e575d] Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 09, 2023 17:40:30.323 [24860] ERROR - [Req#e57c5] Format [JPEG] - Insufficient memory (case 4)
Feb 09, 2023 17:40:30.596 [6896] ERROR - [Req#e57c8] Format [JPEG] - Insufficient memory (case 4)
Feb 09, 2023 17:40:32.807 [21520] ERROR - [Req#e57db] Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 09, 2023 17:40:32.970 [21520] ERROR - [Req#e5741] Format [JPEG] - Insufficient memory (case 4)
Feb 09, 2023 17:40:32.972 [15756] ERROR - [Req#e5742] Format [JPEG] - Insufficient memory (case 4)
Feb 09, 2023 17:40:33.016 [6896] ERROR - [Req#e57f8] Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 09, 2023 17:40:33.090 [6896] ERROR - [Req#e57f5] Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 09, 2023 17:40:33.380 [6896] ERROR - [Req#e5802] Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 09, 2023 17:41:01.471 [15524] ERROR - [Req#e5838] Format [JPEG] - Insufficient memory (case 4)
Feb 09, 2023 17:41:01.507 [12992] ERROR - [Req#e5837] Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 09, 2023 17:42:07.094 [23692] ERROR - [HttpClient] Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 09, 2023 17:42:07.660 [23692] ERROR - [HttpClient] Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 09, 2023 17:42:08.197 [23692] ERROR - [HttpClient] Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 09, 2023 17:42:08.719 [23692] ERROR - [HttpClient] Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 09, 2023 17:42:09.262 [23692] ERROR - [HttpClient] Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 09, 2023 17:43:03.166 [25864] ERROR - [HttpClient] Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 09, 2023 17:43:08.081 [25864] ERROR - [HttpClient] Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 09, 2023 17:43:08.438 [25864] ERROR - [HttpClient] Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 09, 2023 17:43:09.400 [25864] ERROR - [HttpClient] Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 09, 2023 17:43:09.698 [25864] ERROR - [HttpClient] Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 09, 2023 17:43:10.085 [25864] ERROR - [HttpClient] Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 09, 2023 17:44:02.565 [26196] ERROR - [HttpClient] Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 09, 2023 17:44:04.188 [26196] ERROR - [HttpClient] Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 09, 2023 17:44:04.373 [26196] ERROR - [HttpClient] Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 09, 2023 20:07:37.051 [22308] ERROR - [Req#ea26a] Format [JPEG] - Insufficient memory (case 4)
Feb 09, 2023 20:07:37.243 [23984] ERROR - [Req#ea26d] Format [JPEG] - Insufficient memory (case 4)
Feb 09, 2023 20:07:38.857 [22308] ERROR - [Req#ea276] Format [JPEG] - Insufficient memory (case 4)
Feb 09, 2023 20:07:40.840 [25364] ERROR - [Req#ea287] Format [JPEG] - Insufficient memory (case 4)
Feb 09, 2023 20:07:44.456 [23984] ERROR - [Req#ea29b] Format [JPEG] - Insufficient memory (case 4)
Feb 09, 2023 20:20:14.771 [24928] ERROR - [Req#ea6b9] Format [JPEG] - Insufficient memory (case 4)
Feb 09, 2023 20:20:27.888 [25444] ERROR - [Req#ea6d0] Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 09, 2023 20:20:27.986 [25444] ERROR - [Req#ea728] Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 09, 2023 21:45:39.629 [25692] ERROR - [Req#ef89a] Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 09, 2023 21:45:39.690 [23732] ERROR - [Req#ef89e] Format [JPEG] - Insufficient memory (case 4)
Feb 09, 2023 21:45:39.714 [25692] ERROR - [Req#ef894] Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 09, 2023 21:47:51.473 [15472] ERROR - [Req#ef8a3] Format [JPEG] - Insufficient memory (case 4)
Feb 09, 2023 22:09:08.324 [16908] ERROR - [Req#f0225] Format [JPEG] - Insufficient memory (case 4)
Feb 09, 2023 22:09:08.561 [24692] ERROR - [Req#f0242] Format [JPEG] - Insufficient memory (case 4)
Feb 09, 2023 22:09:32.468 [12820] ERROR - [Req#f02a1] Format [JPEG] - Insufficient memory (case 4)
Feb 09, 2023 22:09:33.733 [24644] ERROR - [Req#f02cf] Format [JPEG] - Insufficient memory (case 4)
Feb 09, 2023 22:09:33.776 [14372] ERROR - [Req#f02cc] Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 09, 2023 22:09:34.428 [14208] ERROR - [Req#f02d0] Format [JPEG] - Insufficient memory (case 4)
Feb 09, 2023 22:09:34.453 [14372] ERROR - [Req#f02d1] Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 09, 2023 22:09:35.551 [14208] ERROR - [Req#f02e2] Format [JPEG] - Insufficient memory (case 4)
Feb 09, 2023 22:09:35.634 [14372] ERROR - [Req#f02da] Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 09, 2023 22:09:35.903 [24644] ERROR - [Req#f02cb] Format [JPEG] - Insufficient memory (case 4)
Feb 09, 2023 22:09:35.904 [14372] ERROR - [Req#f02c9] Format [JPEG] - Insufficient memory (case 4)
Feb 09, 2023 22:09:54.650 [12820] ERROR - [Req#f0312] Format [JPEG] - Insufficient memory (case 4)
Feb 09, 2023 22:09:54.732 [16696] ERROR - [Req#f031e] Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 09, 2023 22:09:55.292 [16696] ERROR - [Req#f031f] Error transcoding photo: bad allocation
Feb 09, 2023 22:18:34.077 [7224] ERROR - [Req#f11b3] Format [JPEG] - Insufficient memory (case 4)
Feb 09, 2023 22:18:34.077 [24208] ERROR - [Req#f11be] Format [JPEG] - Insufficient memory (case 4)
Feb 09, 2023 22:18:43.867 [24208] ERROR - [Req#f1220] Format [JPEG] - Insufficient memory (case 4)
Feb 09, 2023 22:18:43.872 [23804] ERROR - [Req#f1229] Format [JPEG] - Insufficient memory (case 4)
Feb 09, 2023 22:18:46.707 [7224] ERROR - [Req#f1246] Error transcoding photo: bad allocation
Feb 09, 2023 22:18:49.549 [7224] ERROR - [Req#f124b] Error transcoding photo: bad allocation
Feb 09, 2023 22:18:50.174 [23804] ERROR - [Req#f1271] Format [JPEG] - Insufficient memory (case 4)
Feb 09, 2023 22:18:50.187 [23804] ERROR - [Req#f1248] Format [JPEG] - Insufficient memory (case 4)
Feb 09, 2023 22:18:50.331 [23804] ERROR - [Req#f1249] Format [JPEG] - Insufficient memory (case 4)
Feb 09, 2023 22:18:51.138 [7224] ERROR - [Req#f1288] Format [JPEG] - Insufficient memory (case 4)
Feb 09, 2023 22:18:51.147 [23804] ERROR - [Req#f1294] Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 01:46:37.197 [26188] DEBUG - IntroDetector: Initializing for "E:\Media\TV Series\Criminal Minds\Season 6\Criminal Minds - S06E14 - Sense Memory WEBDL-1080p.mkv" (63139)
Feb 10, 2023 02:34:46.540 [26188] DEBUG - Updating part with ID=210135 [E:\Media\TV Series\Criminal Minds\Season 6\Criminal Minds - S06E14 - Sense Memory WEBDL-1080p.mkv]
Feb 10, 2023 02:34:46.543 [26188] DEBUG - Doing expensive tags write for 'Sense Memory' because something changed.
Feb 10, 2023 05:03:46.988 [25384] ERROR - [Req#11885b] Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:43:47.944 [10332] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:44:08.919 [14840] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:44:51.494 [14840] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:44:56.570 [17992] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:45:24.433 [10332] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:45:40.961 [10332] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:45:49.501 [18444] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:45:49.509 [18444] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:46:05.832 [26188] DEBUG - Loaded metadata for You Wanna Make A Memory (ID 54785) in 1ms
Feb 10, 2023 06:46:27.510 [14840] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:46:27.518 [14840] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:46:29.449 [10332] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:46:29.457 [10332] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:46:38.368 [18444] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:46:44.554 [18444] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:46:53.961 [17992] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:46:57.865 [14840] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:46:57.873 [14840] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:47:01.113 [14840] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:47:08.679 [14840] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:47:09.321 [17992] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:47:18.004 [14840] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:47:19.192 [14840] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:47:32.129 [18444] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:47:33.143 [10332] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:47:51.775 [18444] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:47:56.280 [18444] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:48:00.288 [18444] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:48:04.135 [18444] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:48:04.143 [18444] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:48:14.215 [17992] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:48:30.536 [14840] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:48:30.545 [14840] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:48:35.069 [14840] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:48:36.601 [10332] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:48:36.609 [10332] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:48:47.341 [10332] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:48:50.933 [10332] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:48:55.401 [10332] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:49:01.155 [17992] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:49:01.163 [17992] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:49:13.073 [18444] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:49:13.735 [18444] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:49:40.660 [18444] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:49:40.668 [18444] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:49:54.257 [18444] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:50:00.694 [14840] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:50:01.809 [10332] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:50:06.158 [10332] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:50:16.680 [17992] ERROR - Got exception from request handler: bad allocation
Feb 10, 2023 06:50:23.239 [17992] ERROR - Got exception from request handler: bad allocation
Feb 10, 2023 06:50:25.345 [14840] ERROR - Got exception from request handler: bad allocation
Feb 10, 2023 06:50:30.093 [26188] DEBUG - Loaded metadata for I'll Keep Your Memory Vague (ID 53030) in 2ms
Feb 10, 2023 06:50:30.104 [18444] ERROR - Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 10, 2023 06:50:30.112 [18444] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:50:32.283 [10332] ERROR - Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 10, 2023 06:50:33.300 [10332] ERROR - Got exception from request handler: bad allocation
Feb 10, 2023 06:50:37.995 [17992] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:50:38.267 [18444] ERROR - Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 10, 2023 06:50:38.274 [18444] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:50:40.396 [18444] ERROR - Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 10, 2023 06:50:41.910 [10332] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:50:41.918 [10332] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:50:42.803 [10332] ERROR - Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 10, 2023 06:50:44.308 [17992] ERROR - Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 10, 2023 06:50:44.315 [17992] ERROR - Got exception from request handler: bad allocation
Feb 10, 2023 06:50:50.851 [14840] ERROR - Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 10, 2023 06:50:57.727 [17992] ERROR - Got exception from request handler: bad allocation
Feb 10, 2023 06:50:58.438 [10332] ERROR - Got exception from request handler: bad allocation
Feb 10, 2023 06:51:01.714 [14840] ERROR - Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 10, 2023 06:51:01.720 [14840] ERROR - Got exception from request handler: bad allocation
Feb 10, 2023 06:51:02.214 [10332] ERROR - Got exception from request handler: bad allocation
Feb 10, 2023 06:51:02.466 [18444] ERROR - Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 10, 2023 06:51:03.076 [18444] ERROR - Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 10, 2023 06:51:03.081 [18444] ERROR - Got exception from request handler: bad allocation
Feb 10, 2023 06:51:08.087 [14840] ERROR - Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 10, 2023 06:51:12.572 [18444] ERROR - Got exception from request handler: bad allocation
Feb 10, 2023 06:51:12.577 [18444] ERROR - Got exception from request handler: bad allocation
Feb 10, 2023 06:51:14.766 [18444] ERROR - Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 10, 2023 06:51:19.045 [14840] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:51:19.051 [14840] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:51:21.874 [14840] ERROR - Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 10, 2023 06:51:23.581 [14840] ERROR - Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 10, 2023 06:51:23.586 [14840] ERROR - Got exception from request handler: bad allocation
Feb 10, 2023 06:51:24.318 [17992] ERROR - Got exception from request handler: bad allocation
Feb 10, 2023 06:51:25.420 [14840] ERROR - Got exception from request handler: bad allocation
Feb 10, 2023 06:51:25.428 [14840] ERROR - Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 10, 2023 06:51:26.816 [14840] ERROR - Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 10, 2023 06:51:26.822 [14840] ERROR - Got exception from request handler: bad allocation
Feb 10, 2023 06:51:27.086 [14840] ERROR - Got exception from request handler: bad allocation
Feb 10, 2023 06:51:27.090 [14840] ERROR - Got exception from request handler: bad allocation
Feb 10, 2023 06:51:32.657 [17992] ERROR - Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 10, 2023 06:51:32.664 [17992] ERROR - Got exception from request handler: bad allocation
Feb 10, 2023 06:51:38.190 [17992] ERROR - Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 10, 2023 06:51:38.198 [17992] ERROR - Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 10, 2023 06:51:39.015 [10332] ERROR - Got exception from request handler: bad allocation
Feb 10, 2023 06:51:39.020 [10332] ERROR - Got exception from request handler: bad allocation
Feb 10, 2023 06:51:44.792 [10332] ERROR - Got exception from request handler: bad allocation
Feb 10, 2023 06:51:44.800 [10332] ERROR - Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 10, 2023 06:51:55.301 [18444] ERROR - Got exception from request handler: bad allocation
Feb 10, 2023 06:51:55.306 [18444] ERROR - Got exception from request handler: bad allocation
Feb 10, 2023 06:51:57.274 [10332] ERROR - Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 10, 2023 06:51:57.280 [10332] ERROR - Got exception from request handler: bad allocation
Feb 10, 2023 06:51:59.267 [17992] ERROR - Format [PNG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 10, 2023 06:52:03.467 [17992] ERROR - Format [PNG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 10, 2023 06:52:06.996 [17992] ERROR - Got exception from request handler: bad allocation
Feb 10, 2023 06:52:07.002 [17992] ERROR - Got exception from request handler: bad allocation
Feb 10, 2023 06:52:07.518 [17992] ERROR - Got exception from request handler: bad allocation
Feb 10, 2023 06:52:07.524 [17992] ERROR - Got exception from request handler: bad allocation
Feb 10, 2023 06:52:13.580 [17992] ERROR - Got exception from request handler: bad allocation
Feb 10, 2023 06:52:13.587 [17992] ERROR - Got exception from request handler: bad allocation
Feb 10, 2023 06:52:14.346 [17992] ERROR - Got exception from request handler: bad allocation
Feb 10, 2023 06:52:14.351 [17992] ERROR - Got exception from request handler: bad allocation
Feb 10, 2023 06:52:15.724 [18444] ERROR - Got exception from request handler: bad allocation
Feb 10, 2023 06:52:16.653 [10332] ERROR - Format [JPEG] - Insufficient memory (case 4)
Feb 10, 2023 06:52:16.967 [18444] ERROR - Got exception from request handler: bad allocation
Feb 10, 2023 06:52:16.971 [18444] ERROR - Got exception from request handler: bad allocation
Feb 10, 2023 06:52:18.786 [14840] ERROR - Got exception from request handler: bad allocation
Feb 10, 2023 06:52:18.791 [14840] ERROR - Got exception from request handler: bad allocation
Feb 10, 2023 06:52:19.635 [10332] ERROR - Format [JPEG] - DIB allocation failed, maybe caused by an invalid image size or by a lack of memory
Feb 10, 2023 06:52:19.641 [10332] ERROR - Got exception from request handler: bad allocation
Feb 10, 2023 06:52:24.355 [14840] ERROR - Got exception from request handler: bad allocation
Feb 10, 2023 06:52:24.361 [14840] ERROR - Got exception from request handler: bad allocation
Feb 10, 2023 06:52:25.892 [18444] ERROR - Got exception from request handler: bad allocation
Feb 10, 2023 06:52:25.897 [18444] ERROR - Got exception from request handler: bad allocation
Feb 10, 2023 06:52:27.063 [18444] ERROR - Got exception from request handler: bad allocation
Feb 10, 2023 06:52:27.150 [4760] ERROR - Exception handled: bad allocation
Feb 10, 2023 06:52:27.151 [4760] ERROR - Thread: Uncaught exception running async task which was spawned by thread 15028: bad allocation
Feb 10, 2023 06:52:27.157 [4760] ERROR - Exception handled: bad allocation
Feb 10, 2023 06:52:27.157 [4760] ERROR - Thread: Uncaught exception running async task which was spawned by thread 15028: bad allocation
Feb 10, 2023 06:52:27.458 [4760] ERROR - Exception handled: bad allocation
Feb 10, 2023 06:52:27.459 [4760] ERROR - Thread: Uncaught exception running async task which was spawned by thread 15024: bad allocation
Feb 10, 2023 06:52:27.466 [4760] ERROR - Exception handled: bad allocation
Feb 10, 2023 06:52:27.467 [4760] ERROR - Thread: Uncaught exception running async task which was spawned by thread 15028: bad allocation
Feb 10, 2023 06:52:28.475 [26188] ERROR - SQLITE3:0x94322876, 7, failed to allocate 85120 bytes of memory
Feb 10, 2023 06:52:28.762 [10332] ERROR - Got exception from request handler: bad allocation
Feb 10, 2023 06:52:30.331 [26188] ERROR - [Lyrics] SQLITE3:0x94322876, 7, failed to allocate 65540 bytes of memory
Feb 10, 2023 06:52:30.334 [26188] ERROR - [Lyrics] Exception inside transaction (inside=1) (E:\jenkins\server\3571781898\Library\ExtraDataMap.cpp:264): sqlite3_statement_backend::loadOne: out of memory
Feb 10, 2023 06:52:30.338 [26188] ERROR - Butler: Uncaught exception running subtask RefreshPeriodicMetadata: sqlite3_statement_backend::loadOne: out of memory
Feb 10, 2023 06:52:32.473 [4760] ERROR - Exception handled: bad allocation
Feb 10, 2023 06:52:32.475 [4760] ERROR - Thread: Uncaught exception running async task which was spawned by thread 15024: bad allocation
Feb 10, 2023 06:52:32.487 [4760] ERROR - Exception handled: bad allocation
Feb 10, 2023 06:52:32.489 [4760] ERROR - Thread: Uncaught exception running async task which was spawned by thread 15028: bad allocation
Feb 10, 2023 06:52:37.248 [4760] ERROR - Exception handled: bad allocation
Feb 10, 2023 06:52:37.249 [4760] ERROR - Thread: Uncaught exception running async task which was spawned by thread 15024: bad allocation
Feb 10, 2023 06:52:37.285 [4760] ERROR - Exception handled: bad allocation
Feb 10, 2023 06:52:37.286 [4760] ERROR - Thread: Uncaught exception running async task which was spawned by thread 15028: bad allocation
Feb 10, 2023 06:52:38.339 [4760] ERROR - Exception handled: bad allocation
Feb 10, 2023 06:52:38.341 [4760] ERROR - Thread: Uncaught exception running async task which was spawned by thread 15024: bad allocation
Feb 10, 2023 10:39:32.389 [25320] ERROR - [Req#13c999] SQLITE3:0x94322876, 7, failed memory resize 262144 to 524288 bytes
Feb 10, 2023 10:39:32.395 [25320] ERROR - Got exception from request handler: sqlite3_statement_backend::loadRS: out of memory
Feb 10, 2023 10:39:32.574 [25320] ERROR - [Req#13c99f] SQLITE3:0x94322876, 7, failed memory resize 262144 to 524288 bytes
Feb 10, 2023 10:39:32.575 [25320] ERROR - Got exception from request handler: sqlite3_statement_backend::loadRS: out of memory
Feb 10, 2023 16:26:49.552 [15028] ERROR - HttpServer: got exception from I/O context: bad allocation

So it is either Plex Media Server was using a lot of memory or some other applications on the system taking all available memory, You could check the amount of memory used by Plex Media Server.exe in Windows Task Manager. Adding the LogMemoryUse would help in establishing if PMS is holding onto a lot of memory

You could also consider switching to the 64-bit build which gets round issues when the process usage gets close to 2Gb - but if the issue is that other applications taking the memory then that would not help

The dump shows that windows was running for close to 4 days before the crash

Hi @sa2000. Has the dev team given any insight as to what my issue might be? Thank you.

Ive been seeing these errors since about december as well. Very annoying. Its happening to me every few days now. Only way to fix it is to reboot the machine plex is on.

In my case the machine is a Windows 10, Intel Core i9 with 32GB of ram and a 1TB SSD. The only software running on this machine is Plex server.

[3092][Req#47dcff] Format [JPEG] - Insufficient memory (case 4)

[3092][Req#47dcff] Error resizing an image, we don’t trust what we cached [C:\Users\xxxx\AppData\Local\Plex Media Server\Cache\PhotoTranscoder\3e\3e2d97ddbd99aa230e31f0326bab88bffbe6eb54.jpg]

Great thank you. I’ve enabled LogMemoryUse. I’ve noticed a couple of different types of crashes. Sometimes the plex tray icon is unresponsive (I right-click it and an empty context menu pops up, when this happens I have to kill the plex server process and start it again), and then some of the other crashes, the plex tray icon (and plex server process) are gone completely.

It doesn’t feel like a system RAM issue as everything else on the system is still working just fine.

I don’t have any update on this. Does not appear to be a widespread crash
Would not mind seeing more examples - so please run with debug logging enabled and get me server logs after the restart following a crash - I can then see from the Plex Crash Uploader logs which files to fetch for me from $TMPDIR - crash uploading does not always succeed even when logged as successful

For the case where the Plex Media Server.exe remains visible in Task Manager, I would need diagnostics for Deadlocks - this would be getting list of connections and process dump and the logs

Diagnostics for a deadlock / lockout (Windows)

  1. Prepare by finding the server security token string as it will be needed for the connections list request. To find the token string, see this support article Finding an authentication token / X-Plex-Token | Plex Support - it is also in the registry as PlexOnlineToken in server settings area

  2. When the problem occurs (and please wait for sufficient time before capturing diagnostics or restarting eg 10 minutes of requests to the server not getting through) , get the output from a specific browser request on the server. In a browser, go to this url http://localhost:32400/connections?X-Plex-Token=xxxxxxxxxxxxxxxxxxxxx where you put the server token string instead of the xxxxxxxxxxxxxxxx. Copy the displayed output to a text file and save

  3. Next is to force a process dump for the Plex Media Server.exe process. We can do this with Windows Task Manager - find the Plex Media Server.exe process, select it and right click on it and choose Create Dump

  4. Check that the dmp file has been created

  5. Restart the server and capture the zipped logs

  6. Zip the dmp files and upload to dropbox / google drive or similar service

  7. send me by private message link to the zipped dmp files and send the saved /connections output text files and the zipped logs

I suggest enabling Memory Usage Logging in server advanced settings in the registry
It is LogMemoryUse with value of 1 and is a DWord (32 bit) and get server logs

and also suggest you switch to the 64-bit build of Plex Media Server

Ok thanks, I did both. will follow up in a week.