Roon 2.0 - Crashing on MacOS due to ".NET ThreadPool Worker" [Ticket In]

Same for me on MacBook with Catalina and very clean installation.
Roon did either not start at all or crashed after 2-3 hours. Now I went back to 1.8 legacy, and it is stable again.

Is there an update on this issue from ROON?
Amy estimated timeline for resolution ?

Thx

I had started another thread, but will try to update here. I’ve tried to run Roon on a MacMini (Intel 2018, Monterey and then Ventura) using the Mac as the Core. The app crashes and takes the Core down with it (I can’t access Roon with my phone, e.g.). Given that, I’ve created a Core on my NAS (RoonOnNAS, Synology DS920+ running DSM7). That Core has been rock solid, but the app on the Mac (which I can use to access the Core) still frequently crashes. The Core is still up on my NAS, though, and I can access it via my phone without a problem. I have uploaded logs for you from the Mac.

MacMini 2014 Intel Catalina 10.15.7
Everything worked fine with Roon 1.8 - Roon 2.0 Build 1182 seems to crash.

Thanks! Brian

See full attached crash reports here -
https://drive.google.com/file/d/1ntmMwZQYoBkFM1qUikNvKip3qCD8zoaV/view?usp=sharing

Thread 0 report inline for SEO


Process:               Roon [10269]
Path:                  /Applications/Roon 2.app/Contents/MacOS/Roon
Identifier:            com.roon.Roon
Version:               1.0 (1.0)
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           Roon [10269]
User ID:               501

Date/Time:             2022-12-27 04:57:21.992 -0800
OS Version:            Mac OS X 10.15.7 (19H1922)
Report Version:        12
Anonymous UUID:        AAEB1251-DAFE-F1FF-F6A1-0BCF08AE78AD


Time Awake Since Boot: 6700000 seconds

System Integrity Protection: enabled

Crashed Thread:        73  .NET ThreadPool Worker

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Application Specific Information:
abort() called

Thread 0:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib        	0x00007fff6f37c872 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6f43d425 _pthread_cond_wait + 698
2   libcoreclr.dylib              	0x000000010a21b182 CorUnix::CPalSynchronizationManager::ThreadNativeWait(CorUnix::_ThreadNativeWaitData*, unsigned int, CorUnix::ThreadWakeupReason*, unsigned int*) + 322
3   libcoreclr.dylib              	0x000000010a21adaa CorUnix::CPalSynchronizationManager::BlockThread(CorUnix::CPalThread*, unsigned int, bool, bool, CorUnix::ThreadWakeupReason*, unsigned int*) + 362
4   libcoreclr.dylib              	0x000000010a21f629 CorUnix::InternalWaitForMultipleObjectsEx(CorUnix::CPalThread*, unsigned int, void* const*, int, unsigned int, int, int) + 2153
5   libcoreclr.dylib              	0x000000010a21f7fd WaitForSingleObjectEx + 77
6   libcoreclr.dylib              	0x000000010a43a1bf CLREventBase::WaitEx(unsigned int, WaitMode, PendingSync*) + 191
7   libcoreclr.dylib              	0x000000010a43ec79 Thread::RareDisablePreemptiveGC() + 345
8   libcoreclr.dylib              	0x000000010a3ce5c0 JIT_RareDisableHelperWorker + 48
9   libcoreclr.dylib              	0x000000010a51239b JIT_RareDisableHelper + 23
10  ???                           	0x000000011e480635 0 + 4803003957
11  ???                           	0x000000011ea57999 0 + 4809128345
12  ???                           	0x000000011e478908 0 + 4802971912
13  ???                           	0x000000011e31d537 0 + 4801549623
14  ???                           	0x000000011a41f9da 0 + 4735498714
15  libcoreclr.dylib              	0x000000010a5115e9 CallDescrWorkerInternal + 124
16  libcoreclr.dylib              	0x000000010a35d9ea MethodDescCallSite::CallTargetWorker(unsigned long const*, unsigned long*, int) + 1530
17  libcoreclr.dylib              	0x000000010a24395e RunMain(MethodDesc*, short, int*, PtrArray**) + 734
18  libcoreclr.dylib              	0x000000010a243c7b Assembly::ExecuteMainMethod(PtrArray**, int) + 395
19  libcoreclr.dylib              	0x000000010a2757b2 CorHost2::ExecuteAssembly(unsigned int, char16_t const*, int, char16_t const**, unsigned int*) + 498
20  libcoreclr.dylib              	0x000000010a22d504 coreclr_execute_assembly + 180
21  com.roon.Roon                 	0x0000000109d4299d mono_jit_exec + 93
22  com.roon.Roon                 	0x0000000109d432ba xamarin_main + 570
23  com.roon.Roon                 	0x0000000109d444a4 main + 52
24  libdyld.dylib                 	0x00007fff6f238cc9 start + 1

Roon Core Machine

Mac OS 10.15.7
Mac Mini, 2012 model
Dual core i5 processor
8 GB RAM

Networking Gear & Setup Details

1 GB Ethernet
Cisco Switch
1 GB fiber Internet

Connected Audio Devices

Primary output is Topping D70S DAC
However, issue appears to be with Roon ARC

Number of Tracks in Library

13,500

Description of Issue

I started using Roon ARC a few weeks ago. Since that time, Roon has been crashing and/ or causing a Kernel panic and causing the Mac Mini to reboot. I notice because I’m access Roon ARC remotely, and it stops working. When I get back to my Mac, there is sometimes a message that Roon has crashed and restarted. I captured this-

Process: Roon [10159]
Path: /Applications/Roon.app/Contents/MacOS/Roon
Identifier: com.roon.Roon
Version: 1.0 (1.0)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Roon [10159]
User ID: 501

Date/Time: 2023-01-11 23:11:43.499 -0500
OS Version: Mac OS X 10.15.7 (19H2026)
Report Version: 12
Anonymous UUID: 7DE8FF98-65CE-EB6A-F33F-952C9CDD56AE

Time Awake Since Boot: 250000 seconds

System Integrity Protection: enabled

Crashed Thread: 56 .NET ThreadPool Worker

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Application Specific Information:
abort() called

Thread 0:: Dispatch queue: com.apple.main-thread

See this thread Roon 2.0 - Crashing on MacOS due to ".NET ThreadPool Worker" [Roon Investigating] - #48 by noris
@moderators please combine?

Hi @Ned_Neece,

This does look like the same issue that others are experiencing. I can combine your thread with others but I want to recommend a workaround in Roon Server.

Roon server would replace your all-in-one application as your core. You can still operate Roon with the all-in-one instance though.

Steps:

  1. Download and install Roon Server from my link here. Once Roon server is installed, you’ll see a Roon icon across your top menu. Click it and select the option to launch at startup.

  2. Take a backup of your database and put it in a safe location.

  3. Go to Roon>Settings>General and log out of your core. Select the newly created instance of a core (Roon server) and log in.

  4. Restore your database.

This should work as a solid workaround and won’t require you to leave the Roon interface up for Roon to function.

Regards,
Wes

2 Likes

Well, I just updated to the latest release, 2.0 build 1193, and it ran for almost 15 minutes before crashing while I was reading the release notes… :frowning:

When it crashes, I let Crash Reporter send the crash report to Apple. Do these get to the developers?

I’m running a 2021 MacBook Pro with an M1 Pro, 32Gb RAM, 2TB SSD, on macOS Ventura 13.1.

Typically, the crashes occur when i’m showing the Queue while playing a playlist or an album, and it happens with either local media or streaming from Qobuz. It also crashes when I’m not even playing any music, from the home screen, or I was just on the settings screen, so it doesn’t seem to be specific to any particular activity, just that the app is open…

I have an Apple One subscription, so I have Apple Music, and am about at the point of canceling both Roon and Qobuz, and just using Apple Music for streaming. It’s not High Res, but it is (mostly) lossless, and it would be better than having to restart the broken app every 20 minutes… It’s just not worth spending $250/year for something that isn’t reliable…

Hey @Brad_Tombaugh,

In case you missed the above info, there is a good temporary workaround while we continue to work on this issue, which is installing Roon Server. Please see Wes’s reply above for the proper steps on how to get this up and running in the meantime :+1:

1 Like

Hi Ben, thanks for re-emphasizing the potential solution via Roon Server. However, not sure this is a solution for those who were successfully able to roll back to 1.8, unless we’re willing to take a chance that it will work on our setup. Since a rollback is apparently no longer available, we’d be stuck with what we get upon updating.

I was the original poster on this thread, though there were several other threads on this issue around the same time, some of which have been merged into this one. Is there anything Roon can add with respect to what you’re doing on this issue and when you expect to resolve. I’ve never even seen confirmation that you’ve found what the problem is. As almost 4 months have gone by with no apparent solution, this indicates to me this is not considered a high priority. Meanwhile , there continue to be additional users reporting this issue, and likely others who have not bothered reporting. A status update would be appreciated.

Well said and articulated Scott.
I tend to agree with you that this issue gets very little priority if at all.
I had an exchange with customer support and they assured me that the technical team working on a solution. That was more than 2 months ago !.
Like yourself I sent data, log files and attempted clean install, etc. In return ZERO response on findings.
It will be nice to get a detailed update from Roon wrt what exactly was done to diagnose the problem and expected timeline for resolution. Extremely disappointing especially given I have a life time license for a product I can’t use. Ridicilous.

Hey @Scott_Purdy,

You most certainly deserve an update!

I can confirm we have found the issue, and very much do consider this to be a high-priority case, as it’s affecting many users. I can’t speak on a specific timeline, but our dev team is currently working on a fix that should be included in a new release soon.

I understand your position here. I did also want to point you in the right direction of the 1.8 Roonserver download just in case you did want to give it a go :+1:

Hi. Same issue. Tried Roonserver but mine constantly (every 10 seconds or so) goes to non responding then running then non responding etc etc so anything connected drops off. So not viable.

Could I ask you to announce on this thread when it has been fixed so I can download and upgrade to 2.0 again. Don’t want to keep trying randomly every time there is an update if it doesn’t fix it.

Thank you!

1 Like

I hadn’t seen this thread when I posted my issue, but it looks like the same. Hopefully you find it soon.

This is the beginning of the crash report in case something jumps out:

-------------------------------------
Translated Report (Full Report Below)
-------------------------------------

Process:               Roon [2488]
Path:                  /Applications/Roon.app/Contents/MacOS/Roon
Identifier:            com.roon.Roon
Version:               1.0 (1.0)
Code Type:             X86-64 (Native)
Parent Process:        launchd [1]
User ID:               502

Date/Time:             2023-01-26 12:03:31.7677 -0500
OS Version:            macOS 13.1 (22C65)
Report Version:        12
Bridge OS Version:     7.1 (20P2059)
Anonymous UUID:        B1953D07-DEE7-B54E-48C3-624D643E112C


Time Awake Since Boot: 1100 seconds

System Integrity Protection: enabled

Crashed Thread:        40  .NET ThreadPool Worker

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000

Application Specific Information:
abort() called

It was up a couple of days but crashed again, in a seemingly similar manner

Crashed Thread:        71  .NET ThreadPool Worker

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000

@benjamin - Any ETA for a fix for this? Literally paid a fortune for lifetime licence and can’t use Roon.

Hey @Darren_Jones-Molyneu,

I don’t have an ETA for you quite yet as things are still under development. I’m sorry to hear that Roonserver is acting up for you as well - if you’d like to take a deeper look into that issue separately, please open a fresh thread and tag me so we can investigate in the meantime. :+1:

This happened after my MacBook Pro sat unused for a while, then pulled up Roon to do some stuff. FYI

Translated Report (Full Report Below)

Process: Roon [92682]
Path: /Applications/Roon.app/Contents/MacOS/Roon
Identifier: com.roon.Roon
Version: 1.0 (1.0)
Code Type: X86-64 (Native)
Parent Process: launchd [1]
User ID: 501

Date/Time: 2023-02-28 13:27:36.3726 -0600
OS Version: macOS 13.2.1 (22D68)
Report Version: 12
Bridge OS Version: 7.2 (20P3045)
Anonymous UUID: E0931547-9F6F-0E25-20D5-C8D0E78B0B7B

Sleep/Wake UUID: 414DF9BC-48E1-4597-A4C3-FEC896F03FF2

Time Awake Since Boot: 46000 seconds
Time Since Wake: 39 seconds

System Integrity Protection: enabled

Crashed Thread: 43 .NET ThreadPool Worker

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000

Application Specific Information:
abort() called

Here is the error packet. Write if I can do more:

HTH John