PMS for Mac (Plex Pass download) crashes on launch with 1.14.0.5465-5470. FIXED in 1.14.1.5487

Server Version#: 1.14.0.5465-425e4ac90
Player Version#: Web Client 3.75.3
macOS Version: 10.14.1 (18B75) – just upgraded from 10.14 yesterday, but was working fine until PMS upgrade

I just upgraded PMS for Mac through the Web UI, and now it crashes (appears briefly in the menu bar, then disappears). I’m attaching logs from the PMS log directory.
Plex Media Server.zip (448.4 KB)

EDIT:
I was able to revert to the non-Plex Pass version, and confirm that this version does not crash.

So, in summary:

  • 1.13.9.5456-ecd600442 dated October 30, 2018: does not crash
  • 1.14.0.5465-425e4ac90 dated November 9, 2018: crashes at startup
1 Like

Had you tried a manual download and a swap out of Plex App from applications. I’m having no issue with same set up.

Yes, here’s what I’ve tried:

  • Upgraded to 1.14.0.5465 through the Web UI (crashed)
  • Replaced with manual download of 1.14.0.5465 from download page (crashed)
  • Replaced with manual download of 1.13.9.5456 from download page (works)
2 Likes

Ok, I do not normally open from menu now due to a secure login but from browser. I can not replicate your issue with chrome Version 70.0.3538.77 . So which Browser and have you tried turning off the browser extensions? I do remember a while ago this was caused by apps that are meters, Example: istat.

I am using the same version of Chrome as you listed, but as I said, the newer version fails immediately on startup (the icon appears and then disappears in the status bar on Mac OS X 10.4.1)

1 Like

Howdy dmorse2112, You do know that 1.14.0.5456 Version is Beta Correct? It may not be 100% for mac yet. if it wont work ide roll back to old version until the new one is verified for Public use. Good Luck Cow }:-o)

Yes I’m aware. I rolled back to the non-Plex Pass version, and it is stable - thanks!

2 Likes

Your welcome

I encountered this issue as well. Upgraded to version 1.14.0.5465 and PMS was crashing shortly after it launched. I’m actually running Mac OS X 10.10.5 (Yosemite.)

It looks like the crash report(s) successfully uploaded to Plex so for now have also rolled back to 1.13.9.5456 and disabled Beta updates until this is resolved.

2 Likes

Thanks @pugu - glad to know it wasn’t just me.

Hopefully the developers are seeing these 1.14.0.5465 crash reports!

1 Like

I’m running Mojave 10.14.1 without issue

Same issue here running 10.14.1 and PMS 1.14.0.5465-425e4ac90

Williams-Pro:Applications william$ ./Plex\ Media\ Server.app/Contents/MacOS/Plex\ Media\ Server libc++abi.dylib: terminating with uncaught exception of type boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::system::system_error> >: Invalid argument ****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: 0F6BF18D-0ABC-4E37-B49A-9EDFC5C67FAA Williams-Pro:Applications williamsisti$ Error starting framework core for /Applications/Plex Media Server.app/Contents/Resources/Plug-ins-425e4ac90/MoviePosterDB.bundle. Error starting framework core for /Applications/Plex Media Server.app/Contents/Resources/Plug-ins-425e4ac90/HTbackdrops.bundle. Error starting framework core for /Applications/Plex Media Server.app/Contents/Resources/Plug-ins-425e4ac90/LastFM.bundle.

efault	19:30:53.588725 -0500	loginwindow	-[ApplicationManager checkInAppContext:refCon:eventData:] |      checked in app : Plex Media Server
default	19:30:53.861040 -0500	launchservicesd	CHECKIN:0x0-0xdf0df 6984 com.plexapp.plexmediaserver
default	19:30:53.862339 -0500	loginwindow	-[ApplicationManager checkInAppContext:refCon:eventData:] |      checked in app : Plex Media Server
default	19:30:53.880740 -0500	Plex Media Server	Current system appearance, (HLTB: 2), (SLS: 1)
error	19:30:53.883958 -0500	Plex Media Server	Unable to load Info.plist exceptions (eGPUOverrides)
default	19:30:53.884381 -0500	Plex Media Server	Post-registration system appearance: (HLTB: 2)
default	19:30:53.894289 -0500	Plex Media Server	NSApp cache appearance:
-NSRequiresAquaSystemAppearance: 1
-appearance: (null)
-effectiveAppearance: <NSCompositeAppearance: 0x6000003d00a0
 (
    "<NSAquaAppearance: 0x6000035e0200>",
    "<NSSystemAppearance: 0x6000035e0440>"
)>
default	19:30:53.960457 -0500	tccd	-[TCCDAccessIdentity staticCode]: static code for: identifier com.plexapp.plexmediaserver, type: 0: 0x7f84e8f22770 at /Applications/Plex Media Server.app
error	19:30:53.970797 -0500	Plex Media Server	        AEGetDescData of non-desc type 'reco' not a good idea
error	19:30:54.691600 -0500	Plex Media Server	nw_path_close_fd Failed to close guarded necp fd 75 [9: Bad file descriptor]
error	19:30:56.105350 -0500	Plex Media Server	nw_path_close_fd Failed to close guarded necp fd 75 [9: Bad file descriptor]
error	19:30:57.028701 -0500	Plex Media Server	nw_path_close_fd Failed to close guarded necp fd 75 [9: Bad file descriptor]
error	19:30:57.030017 -0500	Plex Media Server	nw_path_close_fd Failed to close guarded necp fd 75 [9: Bad file descriptor]
error	19:30:57.031224 -0500	Plex Media Server	nw_path_close_fd Failed to close guarded necp fd 75 [9: Bad file descriptor]
error	19:30:57.142728 -0500	Plex Media Server	nw_path_close_fd Failed to close guarded necp fd 75 [9: Bad file descriptor]
error	19:30:57.779931 -0500	Plex Media Server	nw_path_close_fd Failed to close guarded necp fd 75 [9: Bad file descriptor]
default	19:30:57.793892 -0500	loginwindow	-[PersistentAppsSupport applicationQuit:] | for app:Plex Media Server, _appTrackingState = 2

Same here. PMS crash shortly after start. Reverted to 1.13.9. Running MacOS 10.14.2 beta.

1 Like

Thanks to all, reverting back to 1.13.9 fixed the crashes, will keep an eye on this thread for when its fixed.

1 Like

Thank you for the diagnostics. There is a problem but it is caused by an Apple Mac OS bug in the network interfaces data. A change in Plex Media Server has been made to circumvent that and the fix will make its way through the release process. It was fixed after the contents of the beta 1.14.0.5468 was defined

1 Like

Would be interested to see what details are in the output from command ifconfig -a

Please do that in terminal and copy the output into a text file and attach here

Thanks

@sa2000 here is the ifconfig output as requested. Thanks for letting us know about the bug and impending fix!
ifconfig-a.txt (2.2 KB)

Thanks

The case i looked at before yours was a multi-homed loopback with two inet entries. I do not see that in your config - not for ipv4 - there are a couple of entries for inet6 (ipv6) - may be that is leading to the crash.

@sa2000 thank you for letting us know about the upcoming fix. Did this fix make it into 1.14.0.5470 which was recently released or should we expect it in an upcoming release? I ask because I attempted to upgrade to this build and it is still crashing.

1 Like

Same for me… still crashes.

2 Likes