Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MacOS crash when opening Reaper. #51

Closed
tylovejoy opened this issue Jun 19, 2022 · 6 comments
Closed

MacOS crash when opening Reaper. #51

tylovejoy opened this issue Jun 19, 2022 · 6 comments

Comments

@tylovejoy
Copy link

Cannot open Reaper with ReaPack (reaper_reapack-x86_64.dylib) placed in the UserPlugins folder.
I posted the exception details at the bottom of this issue. Here is the full crash output https://pastebin.com/3A9hEjcP

Versions:
MacOS 11.6.7
Reaper 6.61
ReaPack 1.2.4.1

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 [661]

@tylovejoy
Copy link
Author

I was using the wrong folder. My apologies.

@cfillion
Copy link
Owner

Fixing the crash, thanks for reporting this!

@Garvilli
Copy link

Garvilli commented Feb 9, 2023

I have this same issue right now on my Mac Mini M1, so what is the right folder?

@cfillion
Copy link
Owner

cfillion commented Feb 9, 2023

This issue was fixed in v1.2.4.2, if you still have a crash on startup with the latest version it could be something else. The correct folder is UserPlugins in REAPER's resource directory (Options > Show REAPER resource path in explorer/finder) as per the user guide. (But it shouldn't crash even if put elsewhere or renamed.)

Please post your crash report so I can investigate your crash.

@Garvilli
Copy link

Garvilli commented Feb 15, 2023

Thank you for the reply and I'm sorry I haven't replied back yet.

There's no crash report as such, just a pop-up with this message:

“reaper_sws-arm64.dylib” can’t be opened because Apple cannot check it for malicious software.
This software needs to be updated. Contact the developer for more information
Safari downloaded this file on 6 February 2023.

I have problems with other pieces of music software on my Mac, but since I'm so very new to MacOS and crazy busy with building our house, I haven't had the patience or stamina to do much about these things, but in general it seems that my Mac has more "safety" settings in place than your average MacOS install.

Since I was mentally abble to reply to you know, I'm going to see if I'm wake enough to troubleshoot this myself, but thank you again for replying to me!

@Garvilli
Copy link

Alright, got it to work!

So apparently what I needed to do was: Control-click the app icon [In this case I guess it's not an app, but whatever] and choose "Open", as explained in this link:
https://support.apple.com/guide/mac-help/apple-cant-check-app-for-malicious-software-mchleab3a043/mac

This has fixed a ton of other issues for me, such as finally being able to activate the license for Kirchhoff EQ that I bought four months ago, and I'm hoping it will finally make me able to properly install Muse-Hub.

MacOS is turning out to be a complete jank-fest!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants