This issue in the other thread has been going on for a long time, is not fixed yet, and seems to affect only some people and machines, so it’s possible that it didn’t affect you in the past and now does. Which would be particularly interesting to investigate what changed. I think Roon has had problems reproducing the issue and hence pinning it down
Same here. Roon Core iMac @ Intel on Catalina and crash 2-4 times per month. MBA @ M1 and Core/Remote/Bridge also one per week comm: Roon not response, must relaunch software.
With 1.6 and 1.7 if im not wrong Roon was rock stable. With 1.8 sometimes crash, after 2.x crash as hell (end-ponts also lost connection with Core!). Unstable. No fun, no good, I want stable soft!
The Roon team is actively investigating this issue and has a ticket with development. Please see the staff post above in yellow here. I’ve merged your reports into the main tracking thread. Thank you for your patience and we’ll post an update here as soon as we have additional workarounds or a timeline to resolution.
I’m wondering if Ventura 13.2.1 fixed it? Not sure when that came out but when 13.2 came out, I lost functioning of my Pioneer Blu Ray Drive but not my Apple DVD drive. My Apple Laptop still had 13.1 and the Pioneer worked fine on it.
Then, 13.2.1 came out and all the drives worked again.
New user and on 14 day trial and despite looking forward to the experience however, lack of stability is making me reluctant to continue past the 14 day trial. Having exactly the same issues running core on M1 Mac Mini with Ventura 13.3.1. Constantly crashing and therefore loosing a connection with any of my other devices I am trying to run Roon app on (ipad, iphone and macbook). Hoping situation is resolved soon (before my trial ends).
Last crash report:
Date/Time: 2023-04-12 21:21:27.596 +0100
End time: 2023-04-12 21:21:54.441 +0100
OS Version: macOS 13.3.1 (Build 22E261)
Architecture: arm64e
Report Version: 40
Incident Identifier: 58A664C0-0778-4FD8-8B3A-1669603E6DF4
Data Source: Stackshots
Shared Cache: EBDDD61C-5DCF-399C-A88B-759EDF197103 slid base address 0x190420000, slide 0x10420000 (System Primary)
Shared Cache: 8925009A-49CC-3DF3-81AB-2CE7614F8C8E slid base address 0x1d2ac4000, slide 0x52ac4000 (DriverKit)
Shared Cache: C4FF191C-1311-3AB3-945E-DBC71BF39DE7 slid base address 0x7ff804f00000, slide 0x4f00000 (Rosetta)
Command: Roon
Path: /Applications/Roon.app/Contents/MacOS/Roon
Identifier: com.roon.Roon
Version: 1.0 (1.0)
Team ID: WU8DGC424P
Is First Party: No
Architecture: arm64
Parent: launchd [1]
PID: 48116
Time Since Fork: 1732s
Event: hang
Duration: 26.85s
Duration Sampled: 4.30s (process was unresponsive for 23 seconds before sampling)
Steps: 43 (100ms sampling interval)
Hardware model: Macmini9,1
Active cpus: 8
HW page size: 16384
VM page size: 16384
Time Since Boot: 372631s
Time Awake Since Boot: 371012s
Time Since Wake: 6344s
Fan speed: 1696 rpm
Total CPU Time: 4.263s (8.3G cycles, 9.2G instructions, 0.91c/i)
Advisory levels: Battery → 2, User → 2, ThermalPressure → 0, Combined → 2
Free disk space: 41.17 GB/228.27 GB, low space threshold 3072 MB
Vnodes Available: 77.94% (196738/252416)
Preferred User Language: en-GB
Country Code: GB
Keyboards: British-PC, British
OS Cryptex File Extents: 4495
Timeline format: stacks are sorted chronologically
Use -i and -heavy to re-report with count sorting
Connor - when do you expect the .NET Thread Worker crash to be fixed by Roon? This seems to have been an issue for months now. I really dont understand why its taking so long to fix this. Too many subscribers have been suffering these frequent crashes on Macs caused by this known issue. Thanks
What is the solution to this problem? I’ve been observing this thread for sometime but have not posted my own experience with Roon Core crashing on Ventura 13.4.1. The crash occurs now and then, the latest today.
I have Roon Core 2 (build 1277). I don’t want to install Roon Server as I do use the interface on my iMac.
Hence the problem!! I use the interface on my Mac frequently. Roon Core’s problem on Ventura is still not fixed. I believe many are still waiting on this. Is there any hint Roon or Apple are closing in on the problem and providing a solution? Thanks.
I don’t mean to lump anything on you! I know you’re another user like myself.
The reply you attached was in March. It’s the end of June and there’s no news yet of a fix from Roon. I’m hoping someone from Roon will notice the activity on this thread and provide us users and update.