# Audio Unit plug-in reports problem to Logic

**URL:** <https://forum.juce.com/t/audio-unit-plug-in-reports-problem-to-logic/52770>\
**Category:** General JUCE discussion\
**Created:** [August 26, 2022, 3:05pm UTC](https://forum.juce.com/t/audio-unit-plug-in-reports-problem-to-logic/52770 "2022-08-26T15:05:32Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![TheWaveWarden](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/thewavewarden/32/13708_2.png) [@TheWaveWarden](https://forum.juce.com/u/TheWaveWarden)\
**Post date:** [August 26, 2022, 3:05pm UTC](https://forum.juce.com/t/audio-unit-plug-in-reports-problem-to-logic/52770/1 "2022-08-26T15:05:32Z")

</div>

Hi all!

I’m experiencing a problem in Logic where on about every 100th editor open (my index finger hurts, halp), Logic will randomly display this message:

```auto
An Audio Unit plug-in reported a problem which might cause the system 
to become unstable. Please quit and restart Logic Pro Trial.

```

![image](https://us1.discourse-cdn.com/flex026/uploads/juce/original/2X/5/518364b081c46d04a43009e5dc28988577a3a15d.png)

I’ve tried to attach with several debuggers, but no exceptions or breakpoints are triggered. Therefore, I’m at loss on how to debug this any further.

When I click on “Recover” the GUI won’t open, but it opens fine on the next try. As it doesn’t crash or anything it isn’t a fatal issue, but leaves a bitter taste nonetheless.

The frequency of the issue seems to increase drastically when I use a Debug build over Release.

Does anyone know what’s going on here?

---

<div class="post-metadata">

**Author:** ![otristan](https://avatars.discourse-cdn.com/v4/letter/o/f0a364/32.png) [@otristan](https://forum.juce.com/u/otristan)\
**Post date:** [August 26, 2022, 3:36pm UTC](https://forum.juce.com/t/audio-unit-plug-in-reports-problem-to-logic/52770/2 "2022-08-26T15:36:12Z")

</div>

I suppose you are on M1  
You need to disable SIP and attach debugger to AUHostingServiceXPC\_arrow once logic is started

---

<div class="post-metadata">

**Author:** ![hugoderwolf](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/hugoderwolf/32/14039_2.png) [@hugoderwolf](https://forum.juce.com/u/hugoderwolf)\
**Post date:** [August 26, 2022, 4:02pm UTC](https://forum.juce.com/t/audio-unit-plug-in-reports-problem-to-logic/52770/3 "2022-08-26T16:02:00Z")

</div>

In Console.app you should be able to find crash logs for AUHostingServiceXPC\_arrow. Usually you’ll find a good hint in the call stack of the crashed thread.

---

<div class="post-metadata">

**Author:** ![TheWaveWarden](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/thewavewarden/32/13708_2.png) [@TheWaveWarden](https://forum.juce.com/u/TheWaveWarden)\
**Post date:** [August 28, 2022, 8:13am UTC](https://forum.juce.com/t/audio-unit-plug-in-reports-problem-to-logic/52770/4 "2022-08-28T08:13:15Z")

</div>

Ah, so I was listening on the wrong process, classic! I found the crash logs in Console.app as well.

Thanks to both of you!

---

<div class="post-metadata">

**Author:** ![rodoortiz](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/rodoortiz/32/9954_2.png) [@rodoortiz](https://forum.juce.com/u/rodoortiz)\
**Post date:** [September 22, 2022, 1:11am UTC](https://forum.juce.com/t/audio-unit-plug-in-reports-problem-to-logic/52770/5 "2022-09-22T01:11:33Z")

</div>

@TheWaveWarden Was it useful for you to look at the console.app crash logs? I’m having the same problem right now with an AU plugin

---

<div class="post-metadata">

**Author:** ![TheWaveWarden](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/thewavewarden/32/13708_2.png) [@TheWaveWarden](https://forum.juce.com/u/TheWaveWarden)\
**Post date:** [September 23, 2022, 8:38am UTC](https://forum.juce.com/t/audio-unit-plug-in-reports-problem-to-logic/52770/6 "2022-09-23T08:38:17Z")

</div>

Hi @rodoortiz, yes the crash log was absolutely useful. I didn’t realize at first that I had to scroll down quite a bit to find the stack frames which are actually relevant. Attaching a debugger will give more information though.

For me the problem ended up being to be that Logic seems to not destroy the editor object when you close it under some circumstances.

---

<div class="post-metadata">

**Author:** ![jemmons](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/jemmons/32/15552_2.png) [@jemmons](https://forum.juce.com/u/jemmons)\
**Post date:** [May 18, 2023, 6:11pm UTC](https://forum.juce.com/t/audio-unit-plug-in-reports-problem-to-logic/52770/8 "2023-05-18T18:11:34Z")

</div>

Anyone else have a problem where no relevant crash logs show up in Console.app? I’m getting this error if I leave Logic open for a few minutes after loading my plugin, but nothing related to Logic or AUHostingService ever shows up in the Console’s Crash Reports or Diagnostics or anything. Is there someplace else I should be looking? Or some way to stop errors from being swallowed into a black hole?

M1 macOS v13.3.1, Logic v10.7.7, JUCE v7.0.5
