Yesterday I tried to open PlexAmp on my Mac and it automatically crashed. I thought it was my computer acting up and needed a reboot, but I was in the middle of important things and didn’t reboot until today. Unfortunately, that didn’t change the behavior. I just can’t run it at all.
It works on my iPhone, the Plex Server also works without any issues. Same with the Plex app (not PlexAmp), it just works.
Any tips?
Update: Luckily I had version 4.10.1 available on my programs folder and I installed that over version Plexamp-4.11.0-x64 (the one that was crashing).
I’m on Catalina 10.15.7
If someone from the team sees this, hope this information helps fix the issue and I will be happy to share the crash reports
We’ve looked into it and it appears to be related to a newer build system, and given the age of Catalina, we’re not sure we will be able to find the time to find a workaround at the moment. I’m really sorry.
Catlina… and Big Sur (11.7.10).
Big Sur user here, too. This hasn’t been a good experience as a long-time Plex customer. You guys seem to have inadvertently knocked out two major OS X releases in one update and not even noticed the fact.
As Mac owners, we get that we can age out of certain applications. My iMac is almost ten years old, so it’s understandable. But there’s PLENTY of supported software still running on Catalina and Big Sur. It’s disconcerting that Plexamp would move on without the devs noticing, and without a good reason. Will the “newer build system” be used for the Plex Player, too, killing it on a few OS X revs? Should we worry about Plex Server next? Maybe. Who knows? No one.
Download page still claims support for Catalina.
Also hitting the same issue, no longer able to start up Plexamp. Error is:
Arthurs-MBP-2-2:MacOS arthur$ ./Plexamp
Main: restoring window state from /Users/arthur/Library/Application Support/Plexamp/window-state-plexamp-main.json
Started Media Service: true
Error: Render process (Plexamp) crashed (11) 
Quitting…
From the Console:
Process: Plexamp Helper (Renderer) [705]
Path: /Applications/Plexamp.app/Contents/Frameworks/Plexamp Helper (Renderer).app/Contents/MacOS/Plexamp Helper (Renderer)
Identifier: Plexamp Helper (Renderer)
Version: 4.11.0
Code Type: X86-64 (Native)
Parent Process: Plexamp [702]
Responsible: Plexamp [702]
User ID: 501
Date/Time: 2024-07-24 18:59:21.874 +0100
OS Version: macOS 11.7.10 (20G1427)
Report Version: 12
Anonymous UUID: A67D9F59-F75D-4891-9B5E-8E9A31037B51
Time Awake Since Boot: 120 seconds
System Integrity Protection: enabled
Crashed Thread: 0 CrRendererMain Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: EXC_I386_GPFLT
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [705]
Thread 0 Crashed:: CrRendererMain Dispatch queue: com.apple.main-thread
0 treble.node 0x000000011541d444 NetworkRequestManager::setEventCallbacks(void ()(void, int, unsigned long, unsigned long), void ()(void, int, std::__1::map<std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator >, std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator >, std::__1::less<std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator > >, std::__1::allocator<std::__1::pair<std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator > const, std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator > > > > const&, int, std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator > const&, std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator > const&, unsigned long, std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator > const&), void ()(void, int, std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator > const&, std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator > const&), void*) + 4
1 treble.node 0x00000001153a4af8 AudioPlayerNode::networkSetRequestCallbacks(Nan::FunctionCallbackInfov8::Value const&) + 488
2 treble.node 0x00000001153a9275 Nan:
:FunctionCallbackWrapper(v8::FunctionCallbackInfov8::Value const&) + 213
3 com.github.Electron.framework 0x0000000107a882c0 0x107a52000 + 221888
–
Let me know if you need more logs, stacktrace etc.
I’m on Big Sur 11.7.10 - unfortunately the highest my mid-2014 MacBook Pro will support…
Where can I download the last version that still works? …and then prevent it auto-updating?
It seems that it’s not just Catalina…
Also, I think this would be good practice:
1 - Allow users to decide if they want auto-updates to be on or off. In this case, it doesn’t make sense that I install a version that works for Catalina, to then open it and it updates to the version that crashes.
2 - Allow users to have access to older versions of the app if they want to revert to a version that works for them.
Maybe you’re not willing to offer support for older versions, and it’s totally understandable, but not everyone can afford buying a new machine, just because Plexamp or some other app(s) stopped working. It’s up to the user to decide how their machine should work and which apps to have installed, even if no longer supported.
Here’s the version that works for me:
What I did to avoid auto updates was I locked the file via Get Info > Locked.
It will show you a window every time you open Plexamp, but just choose Cancel and maybe leave the app open all the time
Perfect! That’s got me running again, many thanks!
Totally agreed regarding your comments on having the option to choose if users want to take auto-updates. If a new version is intentionally not going to be compatible with a machine, then it should gracefully decline from installing it. Other apps simply warn you that you’re not going to get any more updates and leave you to run the last compatible version - a few more preferable approach.
I saw that there’s a new version available v.4.11.1
Anyone here knows if this issue has been fixed? So far I’ve been using 4.10.1, because that’s the one that works, but I wonder if they have fixed this?
EDIT: Decided to take a leap of faith, made a copy of the 4.10.1 version just in case, updated and it’s working on Catalina. Since I have the older version as a backup, I’m leaving this one unlocked and available for updates. Hopefully this will not happen again anytime soon. Glad that it was fixed, though.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
