Another freeze and then crash. This time playing from a playlist.
Faulting application name: Roon.exe, version: 1.0.0.0, time stamp: 0x62a332af
Faulting module name: System.Core.ni.dll, version: 4.8.4515.0, time stamp: 0x624cf626
Another freeze and then crash. This time playing from a playlist.
Faulting application name: Roon.exe, version: 1.0.0.0, time stamp: 0x62a332af
Faulting module name: System.Core.ni.dll, version: 4.8.4515.0, time stamp: 0x624cf626
Playing from a playlist to system output, on playlist screen, Roon maximised (I think), froze when Roon window brought to front/focus then crashed.
1/07/2022 4:49:31 PM
Faulting application name: Roon.exe, version: 1.0.0.0, time stamp: 0x62a332af
Faulting module name: System.Core.ni.dll, version: 4.8.4515.0, time stamp: 0x624cf626
From Roon log:
07/01 16:49:29 Debug: render area size changed value: 2560x1369
07/01 16:49:29 Trace: [dbperf] flush 0 bytes, 0 ops in 4 ms (cumulative 127826854 bytes, 99577 ops in 45566 ms)
07/01 16:49:29 Trace: [dbperf] flush 0 bytes, 0 ops in 1 ms (cumulative 127826854 bytes, 99577 ops in 45567 ms)
07/01 16:49:29 Debug: unhandled selection type:
Processor AMD Ryzen 3 3200G with Radeon Vega Graphics, 3600 Mhz, 4 Core(s), 4 Logical Processor(s)
Faulting application name: Roon.exe, version: 1.0.0.0, time stamp: 0x62a332af
Faulting module name: clr.dll, version: 4.8.4515.0, time stamp: 0x624ce98e
Exception code: 0xc00000fd
Fault offset: 0x000000000000b6b4
Faulting process id: 0x4fdc
Faulting application start time: 0x01d88c8383123f64
Faulting application path: C:\Users\AppData\Local\Roon\Application\Roon.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
3 freezes and 2 crashes today with the last crash losing the endpoint and it no longer being available or visible.
Faulting application name: Roon.exe, version: 1.0.0.0, time stamp: 0x62a332af
Faulting module name: System.Core.ni.dll, version: 4.8.4515.0, time stamp: 0x624cf626
Faulting application name: Roon.exe, version: 1.0.0.0, time stamp: 0x62a332af
Faulting module name: clr.dll, version: 4.8.4515.0, time stamp: 0x624ce98e
This issue has been ongoing for MONTHS (way before April 24). The triggered event is always the same: resuming from a minimized window and it’s preceded by a freeze of about 5 seconds.
Fingers crossed. I have had no freezing or crashes of Roon on Windows 10 since today’s updates to builds 987 and 988.
Looking good here too. There was an update to windows 11 as well but you need to manually request it. The two seem to have cured it for me.
Momentary freeze of a few seconds just now.
just installed the latest 988 update
sorry guys but the issue remains the same
It’s much improved for me, but not back to “perfect.”
1 day does not make a trend or provide a conclusion but i had no crashes but did have a few freezes.
You can decide if its fixed. I will continue to provide feedback of my experience
Roon just locked up my Dell XPS 15 Windows 10 while looking at Versions. Nothing was playing. Had to do Ctrl-Alt-Del to shut down frozen Roon.
Since release 752 I had also problems with the windows remote on an older Acer laptop with two graphic cards (Intel and NVidia).
After deciding to use the newest driver from NVidia and change the default graphic card to NVidia for the Roon remote, the problems disappears.
Still freezing for me since latest update!!!
There is no change in the behavior with the latest build/hotfix for me. Start it playing, minimize Roon, work in other windows for an hour and maximize Roon and it will pretty much 100% hang for 10-15 seconds and then crash. If you don’t minimize the Roon window it behaves much better. It will still occasionally crash (usually if the computer has gone to the lock screen, which more or less minimizes all the windows anyway.)
Still freezing and crashing for me since latest update!!!
First time in months i had a whole day without a crash (yesterday). But a new day brings me disappointment. Still crashing and freezing with newest update.
Exactly same behavior as @Christian_Schock states
After 10 days error free (with very light use of PC during this period), first a freeze and crash after a playlist had finished and Roon either maximised or brought to front, and then a second crash the next day on waking up the PC.
Last two lines from log:
07/11 23:36:31 Debug: render area size changed value: 2560x1369
07/11 23:36:31 Debug: GMS: saving nav stack
Faulting application name: Roon.exe, version: 1.0.0.0, time stamp: 0x62c5f2b8
Faulting module name: clr.dll, version: 4.8.4515.0, time stamp: 0x624ce98e
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Selection of Debug entries from a length log file:
07/12 12:53:15 Debug: render area size changed value: 2560x1369
07/12 12:53:16 Debug: [easyhttp] [278] GET to https://internetradio.roonlabs.net/2/api/location?format=msgpack& returned after 983 ms, status code: 200
07/12 12:53:17 Debug: [broker/filebrowser/volumeattached] found newly mounted drive at I:
07/12 12:53:17 Debug: [easyhttp] [286] POST to https://discovery.roonlabs.net/1/query returned after 428 ms, status code: 200
Faulting application name: Roon.exe, version: 1.0.0.0, time stamp: 0x62c5f2b8
Faulting module name: clr.dll, version: 4.8.4515.0, time stamp: 0x624ce98e
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Report
Hello,
I am new to Roon and really love it when it works. However I am running into an issue where yhe Windows app will work for about 2 hours and then crash. When I try to reload it the program freeezes and doesnt repsond. Any ideas what could be causing this?
I have deleted Roon and redownlaoded and I also updated the firewall settings so that Roon is allowed.
Any help would be appreciated as I love the UI but may just cancel.
Hi everyone,
While we’re narrowing down the potential cause of this ongoing issue with our QA team, we have yet to release a precise fix for this issue.
I strongly recommend updating to the most recent build of Roon regardless, as there are unrelated fixes included that will otherwise improve performance and may in many cases reduce the symptoms on affected Cores.
Thank you to those of you who have submitted reports. I recognize the problem is ruinous to the listening experience for those who experience it. Rest assured it remains a top priority to fix.
We’re meeting daily to try to hammer out a workaround and permanent solution, and I will continue to provide updates here.