Roon Remote 2.55+: Crashes on Windows 10 during queue view scrolling (ref#DX1TL1) [Ticket In]

Support
1

What’s happening?

· I am experiencing freezes or crashes

How can we help?

· I am experiencing freezes or crashes

Other options

· Other

Describe the issue

Roon remote 2.55 crashes when scrolling up more than a few pages (via mouse and PageUp) in the "queue" view on Windows 10. It always happens at the same place, just as it should pull in the next album before a particular one.

10/21 22:41:58 Error: Exception updating widget queuelist(1700) > stackpanel(1750/0) > vpanel(1752) > hpanel(1777) > vpanel(1791) > hpanel(1794) > label(1799)
10/21 22:41:59 Info:
Local Time: 10/21/2025 22:41:58 -07:00
Device Serial Number: 7C573CD0-0B41-45C1-B1AC-80B34FA44727
User Id: 7f94462e-313f-4969-8809-54a9eba05e69
Roon Version: 2.55 (build 1559) production
OS Version: Windows 10

Application Domain: Roon
Assembly Codebase: file:///C:/Users/David/AppData/Local/Roon/Application/205501559/Roon.dll
Assembly Full Name: Roon, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null

CPU0 Description: Intel64 Family 6 Model 143 Stepping 8 2016 MHz (64-bit)
CPU0 Num Cores: Physical: 12 Logical: 24

GPU0 Description: Microsoft Basic Display Adapter 0 MB
GPU0 Video Mode:
GPU0 Driver Version: 10.0.19041.3636

GPU1 Description: Intel(R) Arc(TM) A580 Graphics 2047 MB
GPU1 Video Mode: 3440 x 1440 x 4294967296 colors
GPU1 Driver Version: 32.0.101.6790

GPU2 Description: NVIDIA GeForce RTX 3090 0 MB
GPU2 Video Mode:
GPU2 Driver Version: 32.0.15.8129

SCREEN0 Name: \\.\DISPLAY1 (primary)SCREEN0 Bounds: 0,0 3440x1440

SCREEN1 Name: \\.\DISPLAY2 SCREEN1 Bounds: -1920,0 1920x1080

--[ BROOSCRIPT EXCEPTION ]-------------------------------------------

Exception Message: Value was either too large or too small for a Decimal.

at ..\ui\historybrowser.broo:22 [1074849:0082] function format_play_pct
at ..\ui\queue.broo:1659 [d27c98:00aa] equation

--[ INNER EXCEPTION ]------------------------------------------------
Inner Exception Source: System.Private.CoreLib
Inner Exception Type: System.OverflowException
Inner Exception Target Site: Number.ThrowOverflowException
Inner Exception Message: Value was either too large or too small for a Decimal.
Inner Exception Data: none

--[ Inner Stack Trace ]------------
System.Number.ThrowOverflowException(TypeCode type)
System.Private.CoreLib.dll, IL 0, N 34
System.Decimal/DecCalc.VarDecFromR8(Double input, DecCalc& result)
System.Private.CoreLib.dll, IL 0, N -803878582
Broo.Runtime.NumberValue.GetString()
Broo.Runtime.dll, IL 0, N 8630610
Broo.Runtime.Interpreter.Run(Scope scope, BrooxCode code, ArgList args, String name)
Broo.Runtime.dll, IL 758, N 2210

--[ OUTER EXCEPTION ]------------------------------------------------
Outer Exception Source: Broo.Runtime
Outer Exception Type: Broo.BrooScriptException
Outer Exception Target Site: Interpreter.Run
Outer Exception Message: Exception in brooscript
Outer Exception Data: none

--[ Outer Stack Trace ]------------
Broo.Runtime.Interpreter.Run(Scope scope, BrooxCode code, ArgList args, String name)
Broo.Runtime.dll, IL 4225, N 16431
Broo.Runtime.Equation.GetValue()
Broo.Runtime.dll, IL 64, N 245
Broo.Runtime.Equation.GetStringValue()
Broo.Runtime.dll, IL 0, N 8412537
Broo.Engine.StringBrooProperty.IfDirtyDoClean()
BrooEngine.dll, IL 101, N 10432763
Broo.Engine.LabelBase._Update()
BrooEngine.dll, IL 674, N 1233039
Broo.Engine.Widget.Update()
BrooEngine.dll, IL 227, N 5483495
Broo.Engine.Engine.UpdateOnce(Int32& dirtyObjectCount, Int32& dirtyWidgetCount)
BrooEngine.dll, IL 155, N 460
Broo.Engine.DeviceTarget.GuiMainLoop()
BrooEngine.dll, IL 323, N 1063
Sooloos.Application.Main(String[] argv)
Roon.dll, IL 2845, N 8035

Describe your network setup

N/A

2

Hey @david_swift,

Thanks for writing in and sharing your report + crash logs! We’ve created a ticket for our development team to investigate further.

In the meantime, we’d be curious to see if performing a Roon database (not Roon Server) may help you. This won’t affect or touch your Roon Server database / settings / library etc:

  • Exit out of Roon
  • Navigate to your Roon Database Location
  • Find the folder that says “Roon”
  • Rename the “Roon” folder to “Roon_old”
  • Reinstall the Roon App from our Downloads Page to generate a new Roon folder
  • Verify if the issue persists on a fresh database before restoring the backup

We’ll be on standby for your reply! :+1:

3

I’ll give it a try. There is a “Roon”, “RoonGoer”, and a “RoonServer” folder. To be clear, you only want me to rename the “Roon” folder, and leave the other two as-is, correct?

4

Hello @david_swift ,

Yes, please try to rename just the Roon folder, as this is the UI aspect of the Roon app. It would be great to know if the fresh Roon app instance also reproduce the behavior. Let us know how this goes!

5

OK, did that and got the same behavior, same spot in the queue. Do you want me to send the logs from this crash?

6

Hello @david_swift ,

Thanks for giving that a try. We’re going to open up a ticket with our developer to look into this further. For the team to try to reproduce this on their end, we kindly ask that you send us your RoonServer database, you can do so by using the below guide, and upload it to the bottom link. Please let us know once the database has been uploaded, thank you!

https://workdrive.zohoexternal.com/collection/gnhz54df9ddffa33d49a3be8619bd6376a5de/external

7

Uploaded - thanks!

8

Thanks @david_swift! Our development team has a ticket in for further investigation.

In the meantime, if you clear your play history and queue history, does the issue still occur?

9

Hi @david_swift,

Can you please confirm whether you’re still experiencing this issue after updating to the latest Roon build (1582)?

https://community.roonlabs.com/t/roon-2-56-and-arc-1-70-are-live/308822/3

We’ll watch for your response. Thank you!

10

I let it update automatically and tried to scroll up in the queue - same crash, same song/album at the top of the queue.

11

Thanks for confirming, @david_swift. There was no fix in the recent update, but we were curious if related work might have changed the symptom.

We’re sorry this one is still out there - development will reach back out as soon as we have additional progress on the ticket. Thank you for your patience.