I’ve already submitted feedback to Apple but just wondering if anyone is having the same issue.
I recently got a new MacBook Pro M1 Max, running Monterey and Xcode 13.
A project that was building fine on Big Sur (M1, Xcode 12), now crashes with the following error:
clang: error: unable to execute command: Segmentation fault: 11
clang: error: clang frontend command failed due to signal (use -v to see invocation)
No other information or specifics. Tens of other projects build without issues.
The crash happens only when arm64 is selected, no crash for x86_64.
I’m also able to avoid the crash if I use -O1 optimization.
If I remove PluginEditor.cpp and PluginEditor.h it also builds fine. However, there’s nothing fancy in this plugin editor, very similar to other projects. And again, Xcode 12 on Big Sur build without issues.
Any idea what could it be?
Did you solve this issue?
I just got the same error.
We also experience spurious segfaults with Apple clang 12 on our CI machines from times to times. I’d say approximately something like 1 of 200 builds. We once started documenting that but could not find a clear pattern. Simply restarting the build usually fixes it. Is the error that you experience reproducible?
After updating Projucer to 6.1.6, one of our plugin always have this error.
But it only occurs in the release build.
I have tried clearing the cache of Xcode and restarting Xcode. Neither worked.
I’m having the same problem with an iOS app. I’m still on 6.1.5, so I don’t think the JUCE update was the culprit. The error only appears on release builds above -01 optimisation. Updating Xcode made no difference.
The issue is still there, only with one specific plugin (all our other plugins are building fine).
There are 2 workarounds I have found, build the project with -O1 optimization or build it on an older M1 MacBook with Big Sur and Xcode 12.
For us it’s not random, it happens all the time. I don’t think it’s JUCE related.
Xcode 13.3 was released yesterday. Did you try it out?
If you can make an example that only uses open-source code, I would be happy to look into this issue.