An audio Unit plug-in reported a problem which might cause the system to become unstable

I'm just getting time to start this exercise, but all the plugins have dates in December 2023 - which would have been when I went through each product/vendor and made sure I had the latest versions. One of those, BIAS FX 2 had dates of November 12 2023 when I hit "show package contents". The main point is all of the ".component" files in the default folder had one of 2 december dates: 12/12, 12/29. There were none in my ~/Library folder.

So the hunt and peck process begins. Thanks for your help!

This is exactly why so many people turn away from logic, I've been using it for many years - I would say the most frustrating thing is that when a plugin becomes unstable they don't tell you which one is not compatible, this means you now have to go through all your plugins and narrow down on which one isn't functioning.

It's an extremely poor system and I wouldn't put my money on logic fixing something like this.

Is there a log or anything to indicate which plug-in is acting up? It seems a bit weird that they don't give any indication (or that they don't know which one it is).

Yes, there is. Go to Utilities > Console. In the Console.app look for Crash Reports.

"Is it really necessary to use several dozens Audio Units in one song?"

It's really a matter of what you're doing. I'm often working from an orchestra template, so dozens of plugins isn't that unusual. I'll often have many instances of the same thing, so maybe not "dozens" of unique plugins, but dozens of instances for sure.

After seeing a post here saying that older plugins may be hijacking memory from newer plugins, I turned off all the legacy AU plugins in the standard Logic Install. So far, that has solved the issue. At the moment I’m on an M1 mini, latest OS, latest Logic minus all but one of the legacy AU plugins. I’ll update if things change.

Apple are making it so you have to use their guitar bass and drum plugins.. I don't use loops and stuff like that so I cant say anything about them but I've paid a lot of money for third party plugins by companies that specialize in Plugins! They work perfect in Reaper.. screw LOGIC pro and their 3rd rate plugins! They spread themselves out to far maybe stick to one thing and be good at it!

Why doesn't Logic at least tell you WHICH PLUGIN is reporting the issue - or in which plugin Logic spotted a condition it didn't like? Are there logs?

Logic Pro > Preferences/Settings > Plugin Manager > Compatibility

You can Reset and Rescan failed plugins, sometimes they work after succeeding the scan. But I would rather update or remove the plugins manually from the components folder on your hard drive.

Don't forget to restart your computer.

This is annoying and I don't recall it happening before 10.8.

Create a backup before updating anything. You can also create a backup of the Logic Version before updating, rename the old version, put the old version back into your Application folder and use several Logic Versions.

Back up Logic Pro for Mac - Apple Support

Go to

Utilities > Console > Crash Reports

I invested a few hours in updating all my plugins and honestly haven't had a problem since. That was still on Logic 10, and so far Logic 11 is working as well.

If I knew where to investigate to get more details and fix this issue...

Go to Utilities > Console.app > Crash Reports

Glad you got a clue as to which plugin is causing the error, even if it doesn't solve your problem.

Contact Brainworx support.

Thanks for the response but

1) i already rescanned long ago when it first started and all passed

2) There were no “failed” to remove

2) this doesn’t speak to Logic identifying the culprit.

As for the back up, the method you described was more than I understand was needed. I DO have a Time Machine drive always connected. I understood that was all that was needed. I’ll look into pulling that.

thanks again

Than you have to do it the hard way....

Move your all your components to another folder. Look in both component folders

/Library/Audio/Plug-Ins/Components/ (the default folder)

and

~/Library/Audio/Plug-Ins/Components/ (the user folder)

Restart your computer, open the song you got problems with.

The error message should not appear. Put some plugins back into the default component folder.

Restart your computer, open the song you got problems with... and so on...

Edit:

The creation date of a component could be a hint. The older the plugin, the more likely it is the culprit.

Ah, of course, thanks!

Unfortunately, in every case the crashed thread points to "JUCE Timer" and several regularly-used plugins are involved—mostly Spitfire (native UI) and SWAM, in my case. Since JUCE is becoming a common framework for plugin development this isn't great... Hopefully they sort out whatever is going on soon, as I can't really do without the plugins involved.

I know JUCE plays a large part in UI development, so I may just trying closing plugin UIs as frequently as possible after I've used them. One thing I have noticed is that the crashes tend to get reported when I return to Logic after having moved focus away from it. So it may have to do with displaying the plugin UI again or becoming the focus for device input after having given it up.

Being on an M1 MBP, so far I no longer get it on Rosetta. However, there ARE some plugins whose website say they are not yet compatible with Apple silicon or that Rosetta must be used. Not obscure plugins, but still. One is Grandeur, a beautiful piano I bought after seeing Sanjay C do his comparison. Spitfire’s BBC Discover orchestra is another. If I go off Rosetta, I get the error, even if I delete those plugins. Still trying to figure this out.