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

Hey.

I know this is an older post and I hope you've resolved your issue by now.

I just wanted to mention that I ran into this issue for the first time today and I managed to resolve it pretty quickly, it might help someone else with the same issue.

When opening Logic Pro X normally, I got this exact message but it was when I tried opening in Rosetta 2, Logic just crashed and gave me the whole report, I'll post a screen shot below, it's unfortunately in my own language but you get the idea.

I do not understand much of it but I figured as the only plug in the report mentioned was "bx_console 9000 J", I'd try deleting it. In case you didn't get report pop up, you could go to Utilities > Console.app > Crash Reports and find the latest Logic Pro X crash report.

I deleted the plug in from my computer and I could finally open my project again without a message nor crash. However, when I reinstalled it and opened up my project, the same message came up again even though the plugin was successfully validated and was used in other projects.

I had to delete the plug in again, open the project and remove the plug in from every track, save, reinstall the plugin and redo all the processing, which really sucks as a lot was already done..

I use:

Logic Pro 11.0.1

Macbook M3 Pro

18GB

Cheers!

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.

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.

1. disable Midi 2.0
2. make sure your plugins are compatible, I hope you didn't use Migration Tool to transfer audio stuff to your new computer.

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.

I have Logic 10.8.1 installed 1 month ago, osX Sonoma 14.4.1, MacBook Pro M2

I was using it fine for a month with a stock plugins, but the day I've installed FabFilter Pro Q-3 and Waves Harmony (demo with mutes) I started having this issue - not sure which one of two caused problem for me, but maybe it will help people here to narrow it down.

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.

Luckily, it seems to have been fixed with Sonoma 14.4.1. I don't experience these issues anymore since I updated.

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.

In my case, what worked to open a project that had this error was to open Logic itself, go to settings -> plug-in manager -> disable failed audio units. At this point, Logic will uncheck the problematic plugin, then save and close. Open the project again, and that's 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

Dunno if you're still having this problem and I don't know if my workaround will apply as it was in garageband. It gave me the same prompt and I found a really rough and potentially harmful way of fixing it. As you open the file spam press the your backspace/delete button. It'll delete whatever track was selected before it gives the audio unit prompt. It'll instead prompt you with the save progress pop-up, if you didn't delete everything hitting cancel then delete right after. When all of it is deleted hit don't save and it'll close out the software. Reopen it and it shouldn't have that issue, HOWEVER; I'm not certain it'll work as smoothly as it did for me. It may just fully delete your file if not careful or by random. Try this with caution.

Dunno if you're still having this problem and I don't know if my workaround will apply as it was in garageband. It gave me the same prompt and I found a really rough and potentially harmful way of fixing it. As you open the file spam press the your backspace/delete button. It'll delete whatever track was selected before it gives the audio unit prompt. It'll instead prompt you with the save progress pop-up, if you didn't delete everything hitting cancel then delete right after. When all of it is deleted hit don't save and it'll close out the software. Reopen it and it shouldn't have that issue, HOWEVER; I'm not certain it'll work as smoothly as it did for me. It may just fully delete your file if not careful or by random. Try this with caution.

Out of desperation - under 10.8, I seemed to have no problems as of about March 2024 using Rosetta. Not my choice, but it was working even with those plugins not yet "M1" compatible.

I backed up, then upgraded to Logic Pro 11 - NOT using Rosetta - ANY 3rd party plugin gives me this error, even those whose vendor say they ARE M1 compatible cause the error.

If you hit "recover" (not quit), it shows the plugin as it tries to recover. That's the closest I've come to knowing which plugin was the culprit. The way I know is because it's on a test project that has NO 3rd party plugins.

I've added a ToneKing plugin to a guitar audio - crash. Use the stock amp sims - no problem. Use a Waves MV2 - crash. Remove it - no problem. I've tried several others - VU meter, RX-10 Guitar noise, etc. Just testing one at a time. Each one crashes.

That's all I have - no solution, no diagnosis. Just some info. Good luck all... Reaper is looking better and better.