Date/Time: 2021-05-03 23:26:49.010 +0200
OS Version: Mac OS X 10.15.7 (19H1030)
Report Version: 12
Anonymous UUID: 4F482E05-D241-0915-D1DE-43A6896C3DDB
The server does nothing but being a PMS. It has been working with no frequent crashes for several months, years I would say, so I think this may be related to this PMS version.
I too, am having transcoder crash at least 2-3 times per day with the same error in console: EXC_BAD_ACCESS (SIGSEGV) this has been happening for the last 2-3 beta updates.
Server Version#:1.23.0.4482
Player Version#:iOS, tvOS, Firesticks
Process: Plex Transcoder [37695]
Path: /Applications/Plex Media Server.app/Contents/MacOS/Plex Transcoder
Identifier: Plex Transcoder
Version: 0
Code Type: X86-64 (Native)
Parent Process: ??? [34792]
User ID: 501
Date/Time: 2021-05-05 00:58:46.407 -0700
OS Version: Mac OS X 10.15.7 (19H2)
Report Version: 12
Bridge OS Version: 4.6 (17P6610)
Anonymous UUID: F2652A7C-2255-48D9-05EB-XXXXXXXXXXX
Time Awake Since Boot: 300000 seconds
System Integrity Protection: enabled
Crashed Thread: 4
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [37695]
Still happening on 1.23.0.4497. I can provide the last crash report if needed. It seems that deactivating hardware acceleration would prevent the server from crashing, but that is a no go for me, as it makes the Mac Mini much more loaded when there is any transcoding. Is this issue being addressed? I would appreciate some feedback from Plex staff.
I’ve posted several posts about this in the .23 releases and still haven’t heard anything from Plex staff. I suppose will have to keep bumping this until they see it.
Same here. its been crashing (terminating) daily since 8th May for me during the nightly maintenance tasks. (2am). Restart in the morning, and it runs fine all day, but then dies again overnight. Nothing obvious in the logs, even with debug on, just seems to stop mid-process, no common file that I can spot.
Process: Plex Transcoder [70842]
Path: /Applications/Plex Media Server.app/Contents/MacOS/Plex Transcoder
Identifier: Plex Transcoder
Version: 0
Code Type: X86-64 (Native)
Parent Process: ??? [63925]
User ID: 506
Date/Time: 2021-05-11 02:08:20.047 +0100
OS Version: macOS 11.3 (20E232)
Report Version: 12
Anonymous UUID: AD21D748-DF21-F22A-F30A-58926D70DE45
Sleep/Wake UUID: CF0528EA-1BC7-4E53-9349-E86C20DF2257
Time Awake Since Boot: 880000 seconds
Time Since Wake: 23000 seconds
System Integrity Protection: enabled
Crashed Thread: 22
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00007fdbba522000
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [70842]
i thought i’d cracked it since the 6 deep analysis logs showed the same files at the end of the log each crash. however, i disabled deep analysis, and the problem continued, so i guess it was just a timing thing.
i’m only able to replicate the crash when plex does the scheduled maintenance - manually triggered scans, optimise etc don’t seem to cause it, although i have had a couple of random other crashes (and now there’s crash reporter log saying too many submissions!).
i’ve gone back to stable (1.22.3.4523) for now, which seems to be working without issue for me, but will watch the forum with interest.
Wonder what it would take to have the Plex folks acknowledge this post…? I am still having random, almost daily crashes… reverting may fix it, however it would also help me forget the issue exists which may not help in the long run.
A solution in the mean time… fire up a VM. Load Ubuntu server on it and install Plex, then just point it to your local libraries. Should get you running without errors till Plex folks help. It’s easy to pass through hardware acceleration if you have the capabilities too.
Otherwise… in the Plex install directory I think there is folder called updates or version if I recall. Could alway revert to an old version till they look into it.
It’s called beta for a reason tho. At least if you are using the Plex pass version. The officially supported version is the public. I bet it works there. Occasionally betas break things.
Being a Plex pass subscriber simply grants access to the beta. You should not expect stable results in any beta.
I never expect a beta product to be stable… My question was how to raise support to validate it truly is an issue that needs to be addressed. If every beta tester hit an issue and reverted back to stable, I believe many more bugs/defects would go un-noticed. just my $0.02.
I was able to get it to crash consistently with a shared user trying to play content. Every single time they would attempt to start playback, the server would crash.
They were using a roku premier and it was trying to buffer the transcode. As discussed earlier in this thread, I disabled hardware acceleration and they were able to start playback. This occurred while another user was also transcoding playback(successfully).
