Randomly, every hour or so, my Roon server will crash. Client music subsequently halts, but can be restarted and will play again for a period of time until the next crash. The information below is shown in Windows' event log: Log Name: Application Source: Application Error Date: 12/9/2024 9:03:18 AM Event ID: 1000 Task Category: Application Crashing Events Level: Error Keywords: User: IRISPC\Jim Computer: IrisPC Description: Faulting application name: RoonAppliance.exe, version: 1.0.0.0, time stamp: 0x670de1ad Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc00000fd Fault offset: 0x00007ff9d62738f9 Faulting process id: 0x0x4C98 Faulting application start time: 0x0x1DB4A5980497C96 Faulting application path: C:\Users\Jim\AppData\Local\RoonServer\Application\RoonAppliance.exe Faulting module path: unknown Report Id: 9cbccd10-ab4f-46ca-8f3b-3537219d1e40 Faulting package full name: Faulting package-relative application ID: Event Xml:
Here are my PC server details: Device name IrisPC Processor 13th Gen Intel(R) Core(TM) i5-13600K 3.50 GHz Installed RAM 64.0 GB (63.7 GB usable) Device ID 664B850D-05D6-4A3D-B5AD-D99D971F8476 Product ID 00330-53242-89740-AAOEM System type 64-bit operating system, x64-based processor Pen and touch No pen or touch input is available for this display
Describe your network setup
Home network is wired, 1 GbE throughout. Various unmanaged switches used throughout house. Very stable for all other typical uses (internet, printers, video playback, etc).
I am having a similar issue. Roon crashed, then starts the scanning and once finished crashes shortly thereafter. Mac Mini M2 core with a very large library.
@Spec You should open your own support topic to get proper attention. The symptoms you are experiencing may be similar but the causes may well be different. Click here → Support and then click the big Get Help button.
Thanks for the report! As an initial first step, can you please test out disabling and removing any Roon extensions you may have active, and let me know if you experience the same crashing in 20 minute intervals?
Our team will enable diagnostics on your Roon Server in the meantime for additional investigation. We’ll be on standby for your reply!
Previously, a raspberry pi running the DietPi OS 24/7 had an instance of TheAppgineer/roon-extension-manager installed. I uninstalled that manager this evening at about 6:00pm. I will monitor my Roon server event manager to see if this eliminates or mitigates the server crash issue. Prior to this change, the server crashes frequently, even if no music is playing as you can see from the screen shot below.
I discovered that I actually had a second instance of TheAppgineer/roon-extension-manager installed on another raspberry pi connected to my living room stereo which is powered off unless in use. I have disabled that extension manager instance also.
However, when the living room stereo is running, its raspberry pi still runs rooExtend extensions written by DrCWO as shown in the image below:
Unfortunately, the problem persists. After making the changes above, I attempted to play a few hours of queued Christmas music, but playback halted spontaneously after about an hour, as shown in the log below. Same apparent diagnostic details.
Last night I physically powered-off all playback nodes in my home except one - the DietPi instance in my den. I began playback of an 8-hour playlist. Music playback stopped at some point throughout the night, yet the server continued to throw exceptions throughout the night, as shown in this event log.
Hi @Jim_Henderson,
Thank you for uploading those logs. It looks like a stack overflow is what’s causing Roon to crash like this. I will make a ticket for this case with our developers. Once we know more we will get back to you here.
Hi @Jim_Henderson,
Our developers have asked for you to reproduce the crash and then send us the crash dump file here. You can find the dump file at this path on your computer %LOCALAPPDATA%\CrashDumps. This file should help us figure out what is causing the issue. Let us know if you need any help locating the crash report. Thank you for your continued cooperation.
After further discussion, we need to escalate your case to senior development for additional analysis - we’ll follow up once this happens. Thanks again for your patience in the meantime!
Engineering has added some verbose logging to the upcoming build release that should pinpoint the failure. While this will unfortunately require additional wait time for next steps, we’re confident that we’ll illuminate the issue sufficiently to deliver a quick fix.
Thank you for your patience. We’ll post updates here.
