New macOS and new Logic Pro 11 — JUCE AUs STILL CRASHING!

MacOSX and iOS
1

Yeah well I guess I knew this already but no matter what Apple does to upgrade and improve their software, as long as the JUCE developers are just sitting idle whilst letting their customers release plug-ins that crash constantly, these crashes will not cease.

Come on, JUCE, WTF? It’s been since at least December that I have been UNABLE TO USE MY PAID COMMERCIAL PLUG-INS THAT USE JUCE FRAMEWORKS.

The Support channels of my plug-ins, Solid State Logic and Eventide are not doing anything about the issue.

I have tried everything, including wiping my M1 mac clean, re-installing Sonoma, re-installing all my plug-ins, re-installing Logic Pro and STILL I have these f*cking crashes:

Crashed Thread:        75  JUCE Timer

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Codes:       0x0000000000000001, 0x0000000000000000

This is on macOS 14.5 and Logic Pro 11 (both released today).

2

I’m not sure this is a JUCE issue, our plugins are built with JUCE and I’ve just tested them with Logic 11 and MacOS 14.5 on my M1 Max.

I’ve also tested plugins by a few other companies that use JUCE, like Polyverse, and everything seems to work correctly with no crashes.

So, I would check with the plugin manufacturer. A crash on “JUCE Timer” doesn’t mean it’s a bug in JUCE, it just means it’s a crashed caused by the way the dev has applied juce::Timer in their plugin.

1 Like
3

I don’t know who is to blame. I have had tickets open with both SSL and Eventide since December and nothing has been done.

I’ve started from a fresh Mac, fresh install, new user with fresh prefs. In all cases when logic is idle for a few minutes, AUs threads are killed indiscriminately and this crashes the AUHostingService.

I have no clue what else to do. Works fine on Intel Mac. Only m1 crashes. Only JUCE plug ins. No others.

If I didn’t like Logic so much I’d switch to Windows, FFS!

4

Hard to say, since everything looks good here with latest Logic and JUCE plugins that I’ve tested (but I don’t own those eventide and SSL plugins).

Usually you have to contact the plugin manufacturer for this. If you can send them a Logic song that shows the problem, that could maybe help them to reproduce it and offer a solution.

5

I did this with SSL months ago. Sent them a project file and step by step instructions on how to spin lock Logic.

(Easy: Create 16 tracks with a channel strip 2 plug in and then delete the tracks one at a time. Logic will freeze).

They still haven’t had any luck fixing it.

Oh well. I may see if I can get my money back.

6

get a symbolicated crash log first?

7

Following what information we have been given on the forum we have already made changes to the JUCE framework that we hope will help but manufacturers would need to update the version of JUCE they are using, rebuild, and release. We can’t force anything on them. Unfortunately that’s not always as simple as it sounds for manufacturers.