[BUG] Roon instantly crashes (no log) when trying to add credits — Roon 1.8 (Build 764)

Support
1

Core Machine (Operating system/System info/Roon build number)

MacMini — 10.14.6 (18G2022)
Roon 1.8 (Build 764)
Roon server running on internal SSD
Roon Library on external Western Digital USB3 rotational drive

Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)

Core ethernet to a cisco SG300-20
Wireless clients attached via Asus Blue Cave

Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)

Ethernet to Marantz 7011
Ethernet to Marantz 612
Ethernet to Devalet Phantom Gold

Description Of Issue

When I try to edit credits to an album from any connected client, clicking the “+ Add credit” instantly crashes roon.

  1. On client, chose an album
  2. Click the three dots under the album and choose “Edit”
  3. In the next window, click the “Edit Album” panel
  4. Scroll down and click on “Edit Credits”
  5. In the next window click “+Add credit”

SEE> Just a flash of the “Choose Artist” add credit window appears as Roon crashes (or is killed). No crash log is generated that I could find.

Console shows:

default 09:21:44.778269-0800 runningboardd Invalidating assertion 262-122-5852 (target:executable<Roon(501)>) from originator 122
default 09:21:44.794964-0800 AirPlayXPCHelper [0x6F7B] Flushing AP metadata because now playing app has changed [com.roon.Roon] → [com.apple.Music].
default 09:21:44.803705-0800 mDNSResponder [R251217] DNSServiceCreateConnection STOP PID39152
default 09:21:44.804205-0800 runningboardd [executable<Roon(501)>:39152] Death sentinel fired!
default 09:21:44.812814-0800 loginwindow -[PersistentAppsSupport applicationQuit:]
default 09:21:44.812840-0800 loginwindow -[PersistentAppsSupport applicationQuit:]
default 09:21:44.812994-0800 runningboardd Invalidating assertion 262-122-5828 (target:executable<Roon(501)>) from originator 122
2

@support Really hoping this will get addressed soon as this has completely blocked my ability to enter important library data.

3

Hey @HaroldChasen,

Thanks a whole lot, not just for reporting this crash, but for following up on it. I’m sorry it took us this long to get back to you.

Your request is now in our technical team’s queue and they’ll get back to you as soon as possible.

I appreciate all the investigation you’ve done so far :pray:

1 Like
4

Hi @HaroldChasen

Would you kindly use the directions found here and send us over a set of logs using a shared Dropbox link (or any other file sharing service).

6

Thanks Dylan, I’ve sent a link to them in a dm to you, cheers!

7

This is fixed for me after updating to (Build 778). Whether it was addressed directly or as a result of addressing a related or other underlying issue, I thank you.

Cheers!

8

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.