LOGIC PRO X Crash & unstable (Process : AUHostingServiceXPC_arrow)

Question

Emmanuel_DE Author

Level 1

7 points

LOGIC PRO X Crash & unstable (Process : AUHostingServiceXPC_arrow)

Hello.

I'm using Logic Pro X (10.7.9) with few apps & plug-ins (Native Instruments, UAD, etc).

My Mac is a MacBook Air M1 2020 with 8GB RAM and 30GB available on HD. My OS is OSX 13.1 Ventura.

I noticed some instability with Logic Pro X and some of my apps. I regularly get a error message :

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

I checked the Console.app for Crash Reports.

Process crashing is AUHostingServiceXPC_arrow, which is Audio Unit Hosting process for app running via Rosetta mode.

Weird thing is every apps & plug-ins involved runs natively on M1 Silicon chips and OSX 13.1 Ventura (I made sure of that via every app info).

I looked around and found no real solution here or elsewhere on the web.

I check compatibility, granted full disk access to every relevant soft, disable MIDI 2.0, check Logic Pro’s Plug In Manager...

Still I get those crashes mostly involving Komplete Kontrol, Kontakt 7 and UAudio Teletronix La-2 in some part of the process.

I also found some articles about disabling system integrity protection temporarily, attaching apps as a get around to apple sandboxing policy, etc

I didn’t try that since it seems too much.

I'm not an expert but I did everything by the book and check the internet for hours (if not days) before posting.

I hope someone can help please ?

MacBook Air 13″, macOS 13.1

Posted on Nov 27, 2023 6:15 AM

Reply

Answer 1

Top-ranking reply

sanlion

Level 1

13 points

Nov 29, 2023 2:41 AM in response to Emmanuel_DE

have you cleared once the audio unit cache ?

Go to ~/Library/Caches/AudioUnitCache/ and delete/drag the file to the trash (or somewhere else to back up for any reason). Next Start Logic (not in Rosetta Mode) will do a rescan and probably the described Problem is gone

Reply

Answer 2

DDV

Level 1

59 points

Apr 7, 2024 2:05 PM in response to DDV

I read that Sonoma 14.4.1 (released in late March 2024) fixed some nasty iLok bug introduced in 14.4, and that 14.4 fixed the crashing (according to other forums) with AUs. So I never risked 14.4.

But since 14.4.1 came out a few weeks ago, I bit the bullet and went to 14.4.1 this morning, and after enduring crashes since 10.8 was released in November 2023, I am finally crash-free!

My advice: if you can, try 14.4.1.

Reply

Answer 3

edavies

Level 1

14 points

Apr 7, 2024 2:04 PM in response to edavies

UPDATE THAT MAY HELP OTHERS: So, after living for months with these AUHostingServiceXPC_arrow hangs and crashes, I finally did something that seems to have made a difference. I thought it was a bit of a flyer at the time, but resetting Logic to its default settings by going to Logic Pro --> Settings --> Reset All Settings Except Key Command Assignments has radically improved my situation. Prior to doing so, I would get a spinning beach ball a few times an hour (the beach ball would either spin indefinitely until I killed off the hung process or would ultimately let me resume my session after several MINUTES). Now, having reset Logic to its default settings, I have had only one hang over the last week. So, obviously, there are still bugs to be squashed, but this relatively painless reset has let me go from constantly frustrated to very happily productive again. I hope this proves helpful to everyone else having the same problem.

Reply

Answer 4

DDV

Level 1

59 points

Apr 7, 2024 8:20 AM in response to Emmanuel_DE

I am also having this issue. ONLY since Logic Pro 10.8.x. and ONLY on arm64 (Apple Silicon/M1)

What I have found is that a kernel process called memorystatus thinks that the AUHostingService (where your plugins run) is IDLE and is KILLING the process.

Here’s the log entry that shows immediately before Logic reports an “unstable” AU:

memorystatus: killing_idle_process pid 9070 [AUHostingService] jetsam_reason->osr_code: 9

and looking at the macOS Kernel source this reveals “osr_code: 9” means JETSAM_REASON_MEMORY_IDLE

So clearly, since Logic 10.8 (or macOS Ventura, which is a prerequisite), the Mac kernel is aggressively trying to kill the AU plugin hosting process.

i tried opening a support case with Apple and they quickly shut me down saying this is a third party issue. Even though this ONLY STARTED ON Logic 10.8.

Reply

Answer 5

yoyoBen

Level 4

3,403 points

Jun 7, 2024 2:45 AM in response to mfritze

mfritze wrote:

The issue is that way too many Audio Units are not fully Apple Silicon compatible, hence the crashes. The only way to deal with this is to isolate the offending Audio Unit and contact the vendor.

yes, and an easy way to isolate the plugin that is causing issues is by using:

Utilities > Console > Crash reports

Reply

Answer 6

sanlion

Level 1

13 points

Nov 29, 2023 12:58 AM in response to Emmanuel_DE

Sorry if i ask this, just to be sure : you have disabled Rosetta Mode in Logic ?

Reply

Answer 7

Emmanuel_DE Author

Level 1

7 points

Dec 29, 2023 3:58 AM in response to Emmanuel_DE

By the way I decided I'll do some cleaning in my setup.

Anything not used on a daily basis goes out.

Free plugs like Celemony Melodyne Essential, Ampeg SVT-VR Classic, Brainworx bx_tuner, UJAM Virtual Drummer DEEP and others.

I got those via buying hardware / software but I don't use it.

I also deactivated a few process that were running in the back and using CPU.

NKTDaemon, NIHostIntegrationAgent and NIHardwareAgent

From what I read on the internet they're kinda mandatory :

NKTDaemon handles updates through Native Access and such.

NIHostIntegrationAgent helps Komplete Kontrol (S61 MK2) keyboard integration.

NIHardwareAgent helps with Maschine (mikro MK3) hardware handling.

They're all Native Instrument related processes (my main plug and apps provider).

Till now I didn't have any problem using basic fonctions though.

I recorded with a mic in Logic, played piano and few plugs via Komplete Kontrol or Kontakt, all fine.

This is really basic so it might not mean much.

I didn't use Maschine or Komplete Kontrol into Logic.

I didn't try to control Logic with them (play, stop, etc).

I'll keep you posted.

Reply

Answer 8

yoyoBen

Level 4

3,403 points

Apr 7, 2024 1:38 PM in response to DDV

I've just revisited my Logic crashes of the last week with the Console.app:

13 crashes in total, all related to AUHostingServiceXPC_arrow.

6 crashes caused by Native Instruments Kontakt 7,

6 crashes caused by several GRM-Tools plugins,

1 crash causes by Waves WaveShell1-AU.

No issues with Ableton 11, when using the same plugins.

MacOS Sonoma 14.4.1, Logic 10.8.1, M2 MBP 14"

Reply

Answer 9

mfritze

Level 1

119 points

Jun 7, 2024 2:26 AM in response to Emmanuel_DE

The issue is that way too many Audio Units are not fully Apple Silicon compatible, hence the crashes. The only way to deal with this is to isolate the offending Audio Unit and contact the vendor.

Reply

Answer 10

Tuck224

Level 1

8 points

Jun 7, 2024 1:56 AM in response to Emmanuel_DE

./com.apple.xpc.launchd/launchd.log.1:2024-06-07 09:48:28.442632 (gui/501 [100011]) <Notice>: service inactive: com.apple.xpc.launchd.unmanaged.AUHostingServic.10285

./com.apple.xpc.launchd/launchd.log.1:2024-06-07 09:48:28.442642 (gui/501 [100011]) <Notice>: removing inactive unmanaged service: com.apple.xpc.launchd.unmanaged.AUHostingServic.10285

./com.apple.xpc.launchd/launchd.log.1:2024-06-07 09:48:28.509593 (pid/96887/com.apple.audio.AUHostingService.arm64e.A4AEED42-3574-444A-B6CA-8E6DECA7303E [10285]) <Notice>: exited with exit reason (namespace: 1 code: 0x9) - JETSAM_REASON_MEMORY_IDLE_EXIT, ran for 17985476ms

./com.apple.xpc.launchd/launchd.log.1:2024-06-07 09:48:28.509601 (pid/96887/com.apple.audio.AUHostingService.arm64e.A4AEED42-3574-444A-B6CA-8E6DECA7303E [10285]) <Notice>: service state: exited

./com.apple.xpc.launchd/launchd.log.1:2024-06-07 09:48:28.509605 (pid/96887/com.apple.audio.AUHostingService.arm64e.A4AEED42-3574-444A-B6CA-8E6DECA7303E [10285]) <Notice>: internal event: EXITED, code = 0

./com.apple.xpc.launchd/launchd.log.1:2024-06-07 09:48:28.509607 (pid/96887/com.apple.audio.AUHostingService.arm64e.A4AEED42-3574-444A-B6CA-8E6DECA7303E [10285]) <Notice>: job state = exited

./com.apple.xpc.launchd/launchd.log.1:2024-06-07 09:48:28.509627 (pid/96887 [Logic Pro X]) <Notice>: service inactive: com.apple.audio.AUHostingService.arm64e.A4AEED42-3574-444A-B6CA-8E6DECA7303E

./com.apple.xpc.launchd/launchd.log.1:2024-06-07 09:48:28.509636 (pid/96887/com.apple.audio.AUHostingService.arm64e.A4AEED42-3574-444A-B6CA-8E6DECA7303E [10285]) <Notice>: internal event: PETRIFIED, code = 0

./com.apple.xpc.launchd/launchd.log.1:2024-06-07 09:48:28.509637 (pid/96887/com.apple.audio.AUHostingService.arm64e.A4AEED42-3574-444A-B6CA-8E6DECA7303E [10285]) <Notice>: job state = removed

./com.apple.xpc.launchd/launchd.log.1:2024-06-07 09:48:28.509644 (pid/96887/com.apple.audio.AUHostingService.arm64e.A4AEED42-3574-444A-B6CA-8E6DECA7303E [10285]) <Notice>: service state: not running

./com.apple.xpc.launchd/launchd.log.1:2024-06-07 09:48:28.763540 (pid/10285 [AUHostingServic]) <Notice>: shutting down

./com.apple.xpc.launchd/launchd.log.1:2024-06-07 09:48:28.763623 (pid/10285 [AUHostingServic]) <Notice>: cleaning up

launchd detect inactive AUHostingService
launchd remove AuHostingService
Logic lost AUHostingService
Logic show "AU~ unstable ~"

Reply

Answer 11

yoyoBen

Level 4

3,403 points

Dec 29, 2023 3:19 AM in response to Emmanuel_DE

A brief explanation but no "solution" except finding the culprit and searching for an update of the plugin...

https://www.logicprohelp.com/forums/topic/151900-what-happens-when-auhostingservice-crashes/

Reply

Answer 12

Emmanuel_DE Author

Level 1

7 points

Nov 29, 2023 1:20 AM in response to sanlion

Hi Sanlion. Yes I did. Thanks for checking anyway. At this point I’m a bit lost so there’s no wrong tip. I should mention I submitted a feedback to Apple an just got a reply. I’ll send them further infos and files and post here if a get a solution.

Reply

Answer 13

Emmanuel_DE Author

Level 1

7 points

Dec 12, 2023 8:43 AM in response to sanlion

So I cleared the cash and it didn't change much.

I didn't have time to test it properly but my system crashed again while I was testing some other plugs.

I was just messing around with Logic loops so It might be easier to identify the problem.

It crashed instantly when I tried to move one plugin from one track to an other on the fly.

The plugin was "Ampeg SVTVR Classic" but I'm not sure this matters.

Again, the process involved is "AUHostingServiceXPC_arrow".

It is suppose to be an Audio Unit Hosting process for app running via Rosetta mode.

Still doesn't make sense since everything runs natively in my set up.

Also, Apple support didn't get back to me so back to square one.

Anyone has any idea please advise.

I'll let you know if anything comes up.

Thanks !

Reply

Answer 14

Emmanuel_DE Author

Level 1

7 points

Dec 28, 2023 6:26 AM in response to shakefists

Nothing yet sorry.

I'm not using Logic much lately. The little I used it, it didn't crash.

Still waiting to hear back from Apple. It's weird they replied so fast at first then went radio silent.

Anyway I'll keep you posted.

Reply

Answer 15

edavies

Level 1

14 points

Mar 12, 2024 3:47 PM in response to zakar37

I too am in the same boat. Multiple crashes per Logic session. AUHostingServiceXPC_arrow is always flagged as the culprit. Running in native mode on an M2 Ultra Mac Studio with 192GB of RAM. No sketchy plugins. Everything is updated to the latest revs. Happy to provide crash logs, process samples, etc. Desperate for some sort of resolution. Thanks in advance for any help anyone can offer.

Reply

LOGIC PRO X Crash & unstable (Process : AUHostingServiceXPC_arrow)

Similar questions