The error in the macOS message looks like a long-standing crash issue that affects some people and Roon haven’t been able to fix yet. There is a partial workaround in this post by installing Roon Server separately on the same machine. It helps some people but apparently not all:
@support: It seems like the year old problem of Roon crashing on the Apple M1Pro MacBook is still an issue?
I’ve been using my iPad to connect to the Nucleus+ without any issues, but I would like to install Roon on my MacBook Pro to utilize some of the advanced search features and other goodies. That’s why I paid for the Lifetime license with Roon. So, my question is, what Roon version should I install now, running Mac OS Ventura 13.5.2?
I would really appreciate some real talk, and a straight answer please. I also hesitated to install Roon ARC for iPhone.
Only Roon might have some numbers, but my impression is that this affects only a subset of people for whatever reason (for whom it is extremely annoying, of course). I think otherwise the thread would be much longer than it already is. I can say that I have used a Macbook Air M2 as the Roon GUI (Core is a ROCK) for a year with Ventura (always whatever was the latest) and now Sonoma. The Roon app ran every day all day, I used it actively for several hours a day, and I experienced this crash twice during this time. Unfortunately you probably can’t know in advance whether your experience will be like mine or like the unfortunate people. But you have the MBP already and an iPad that works, so no harm in trying.
Hi Suedkiez. I think I was one of the first to experience this error on my MacBook Pro way back, and it just kept crashing all the time until I bought the Nucleus. Had to go to the iPad after the frustration of dealing with no action taken by Roon Support. I would look at the threads that mentioned they are working on a fix., with no resolution in sight. That’s really unfortunate. I expected better. I’m afraid to install it again on my MacBook until I see otherwise that there has been some definite action taken to fix the crashes.
Yeah it sucks, but why would you be afraid? I understand you have a Nucleus and an iPad where it works. Either it works on the Mac or it doesn’t, and if it still crashes for you, you go back to using the iPad?
1 Like
Agreed! I will attempt it on my MacBook and keep you posted. Appreciate the encouragement!
Thanks to all the user community members who have reported their continuing issues with this bug that I, along with others originally reported over a year ago. Extremely disappointing that there is no fix, and no additional communications from Roon support since early this year.
I have been stuck on version 1.8 since I was able to roll back and it still works. Seems like the Roon Core “solution” suggested maybe worked for some, but others report crashes with it as well. However, being stuck on a non-supported version exposes me to the app stopping working in the future, due to things like MacOS updates which frequently cause problems, so this is not a sustainable solution.
I can only conclude that this issue is no longer a high-priority issue that Roon support once indicated it was, or that the difficulty of the fix is beyond the technical capabilities of the programming staff. Either way, an unaccptable level of support for what is an increasingly expensive product given the fact that most of my music collection is now available on streaming services in various forms of hi-res.
Regretably, I’ve made the decision to leave Roon at the end of my current subscription period. I’ve spent dozens of hours exporting and cleaning up my liibrary, which was a complete mess due to backups, reinstalls, exports, re-imports, etc. during my attempts to get a workable Roon solution. I will sacrifice some of the music discovery experience that I found so enjoyable when I initially joined Roon, and getting a lossless streaming solution on all my gear may be more of a challenge or less convenient, but in the long run, I doubt I’ll miss Roon much given the technical issues I’ve experienced from time to time.
Scott
2 Likes
On Sonoma 14.1 Roon streaming to an Oppo is basically unusable. Keeps crashing.
Thread 0:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x18bea40ac __psynch_cvwait + 8
1 libsystem_pthread.dylib 0x18bee15fc _pthread_cond_wait + 1228
2 libcoreclr.dylib 0x104696b48 CorUnix::CPalSynchronizationManager::ThreadNativeWait(CorUnix::_ThreadNativeWaitData*, unsigned int, CorUnix::ThreadWakeupReason*, unsigned int*) + 308
3 libcoreclr.dylib 0x1046967b8 CorUnix::CPalSynchronizationManager::BlockThread(CorUnix::CPalThread*, unsigned int, bool, bool, CorUnix::ThreadWakeupReason*, unsigned int*) + 356
4 libcoreclr.dylib 0x10469a8cc CorUnix::InternalWaitForMultipleObjectsEx(CorUnix::CPalThread*, unsigned int, void* const*, int, unsigned int, int, int) + 1656
5 libcoreclr.dylib 0x10469aaac WaitForSingleObjectEx + 80
6 libcoreclr.dylib 0x10489130c CLREventBase::WaitEx(unsigned int, WaitMode, PendingSync*) + 192
…
Not sure if the devs have made any progress on this, or if they’re even trying, but I’ve noticed something new about the crashes. I’ve had Roon up and running (not playing music) for a day or two on my Intel-based MacPro running Sonoma 14.0.
Roon didn’t crash in that timeframe.
Until I opened Apple Music. Then it crashed within ten seconds. I tried it again. Closed Apple Music, opened Roon, and let it sit idle for a bit. Then I opened Apple Music again. And, 24 seconds later, Roon crashed with Crashed Thread: 54 .NET ThreadPool Worker
I can attach the report if it helps, but is there some sort of contention with the iTunes library folders causing the crashes?
1 Like
Hi @jamiesmithnc,
That’s an interesting observation, thanks for reporting.
As Roon 2.0.25 (build 1353 production) is still rolling out could you share what version of Roon this was with?
Thanks for confirming the build number.
The new build is on slow roll out, looks like it’s not “hit” your machine yet, but it should in the next few days. See release notes below.
Once it does and you have updated, could you repeat the test and report back as I think it will be a very useful datapoint for Roon’s @support and dev teams.
Looks like an update just hit for me. 2.0 (build 1353), I’m assuming that’s the 2.0.25 you mentioned? I’ve got it and Apple Music open, and no crash thus far… fingers crossed
Whelp, that didn’t take long, I guess that it’s still not fixed. 
The “RoonAppliance” has crashed three times already
502 6539 1 0 11:55AM ?? 3:46.27 /Applications/Roon.app/Contents/MacOS/Roon
502 6540 6539 0 11:55AM ?? 0:04.23 /Applications/Roon.app/Contents/MacOS/RAATServer
502 6541 6539 0 11:55AM ?? 0:04.96 /Applications/Roon.app/Contents/Resources/../RoonServer.app/Contents/MacOS/RoonServer
502 7401 6541 0 12:39PM ?? 1:17.88 /Applications/Roon.app/Contents/RoonServer.app/Contents/RoonAppliance.app/Contents/MacOS/RoonAppliance
502 7402 6541 0 12:39PM ?? 0:00.01 /Applications/Roon.app/Contents/RoonServer.app/Contents/MonoBundle/processreaper 7401
With the same .NET ThreadPool worker in the console:
Translated Report (Full Report Below)
-------------------------------------
Process: RoonAppliance [5085]
Path: /Applications/Roon.app/Contents/RoonServer.app/Contents/RoonAppliance.app/Contents/MacOS/RoonAppliance
Identifier: com.roon.RoonAppliance
Version: 1.0 (1.0)
Code Type: X86-64 (Native)
Parent Process: RoonServer [5033]
User ID: 502
Date/Time: 2023-11-14 11:13:45.4073 -0500
OS Version: macOS 14.1.1 (23B81)
Report Version: 12
Bridge OS Version: 8.1 (21P1069)
Anonymous UUID: B1953D07-DEE7-B54E-48C3-624D643E112C
Time Awake Since Boot: 1300 seconds
System Integrity Protection: enabled
Crashed Thread: 51 .NET ThreadPool Worker
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6
Terminating Process: RoonAppliance [5085]
Application Specific Information:
abort() called
...
I can attach a full report if you’d like.
ALSO: A few seconds after I (re)opened apple music (AKA the new iTunes) the RoonAppliance process crashed again (so, four times now).
I’ve got Roon open now, doing nothing because it keeps dropping the music stream, but I do have Apple Music closed to see if the RoonAppliance process stays open.
Thanks for the update … Roon will see it but I’ve also messaged them.
1 Like
Last tidbit, it did crash again, even without Apple Music running-- but it’s entirely possible that stuff going on in the OS are mimicking something that Apple Music does on its own, so I won’t say its unrelated.
Hey @jamiesmithnc,
Thanks for your reporting and your updates so far. Our team is very much still looking into this issue, and while this recent optimization doesn’t contain the fix needed, it will ultimately help pave the path toward a solution.
@Scott_Purdy I understand where you’re coming from and am sorry to hear this issue specifically was the cause for your departure from Roon. Let me assure you that it’s still very much a high-priority issue for our team, and that we’re still eager to find a solution. If it’s ok with you, I can keep you updated on any progress we make - I’ll reach out via private message if that’s something you’d be interested in.
I will be in touch with any new information. 
Benjamin, with all respect, it’s a little hard to take assurances that this is a high-priority issue seriously when it is over a year later and Roon is still not working properly. I’m a paid-up lifetime subscriber, so right now, I’m not getting the benefit from what I’ve paid you.
I tried to play an album this evening to AirPlay speakers, and this is what I was greeted with. These are the crash logs from my server Mac.
Interesting that it’s every five minutes like clockwork.
The standalone server has been working better when playing to my Trinnov Altitude 16, but that’s only available in one room.
Also, by the way, I read the announcement about 2.0.25, but it’s not clear to me what the process is for those of us who installed Roon Server in the hopes that it would help.
2 posts were split to a new topic: Roon on my Mac 14.1.2 is stuck on “Initializing”
Now Roon is completely unusable, with constant .NET ThreadPool worker crashes. When will this get fixed? I’ve got it set up with the new version, with the “RoonServer” and the “RoonAppliance” running (well, trying to)
It’s crashing more than it ever had been. It started the other day, and apparently stopped trying to restart itself. It was crashing when I tried to reopen it today, so I tried the OS update to 14.2, but that didn’t help
