hi guys / @noris my iMac is my core. I do not have problems with having to close and reopen the UI each time it happens, what I do not like is that as I close the “UI” that will terminate my core service as well, is there a way to only close the UI without terminating the core processes?
edit: Never tried cmd+w lol… only cmd+q… next time it happens I will do cmd+w and will let know if that helps.
Thank you for your reports and videos. I have been discussing your thread with the QA team today and we would like to verify if this issue isn’t by any chance due to your PCs running out of resources.
When this behavior occurs, can you please check your Mac Activity Monitor? Do you see any abnormally high CPU/GPU usage? You should be able to view this info in Activity Monitor -> Window -> GPU History and Activity Monitor -> View -> GPU Processes -> GPU Column, please share screenshots of this window when you’re next in the problematic state.
Hi @noris Thanks for keeping taking care of this, next time it happens I will take a video showing the resource monitor, I don’t think it is the case a machine with 6 cores and 40gb of ram which is mainly running only safari and Roon will go out of resources.
Actually, I have discovered something lately, let me try to explain it:
I never considered cmd + w as an option, so I waited it to happen, then bang happened, so I did cmd + w to close the Roon interface but not the process and the macOS UI slowness went away!
I normally run Roon in a secondary desk space (not physical monitors), so I discovered that if I do move Roon to the primary desk space the issue goes away without having to close the Roon window or process, now if move Roon back to let’s say desk 3 the issue will start.
I cleared my Image Cache about 15 minutes ago… looks promising it went back from 20-25% idle while experiencing no UI slowness issue to 2-7% (even less), both in full screen or running in a secondary desk space!
@noris I got some questions, hope you can discuss with QA:
1-can you please find out what relation these option has with the GPU issue?
2-should I modify the current value (256) given the GPU usage issue?
3-how often should I clear the Image Cache in my iMac core?
Hi @noris on Sunday, quite desperate I did backed up my DB (the one I have been constructing since I started with Roon in November) completely uninstalled Roon, and deleted the library folder as well… rebooted, fresh installed Roon, then started configuring Roon to see if the issue is DB related in any way.
by Sunday evening Roon cataloged all my 36000+ files, started playing for an hour or so… Monday I didn’t played any music, then today woke up early, started playing at 6AM then around 7.30am the issue started happening…
This issue looks to have No DB relation, rolling back to my real DB.
This last time I was navigating the albums context menu, filtering some genres with focus, but it is not you can just go there and reproduce it, has happened while in other context menus I am sure.
Thank you for providing the additional information. It sounds like this issue is specific to the hardware since the issue also reproduced with the fresh database, so I will provide the new information we have gathered to QA and let’s see what they say. Once I hear back, I will reach out once more, thanks!
I appreciate your patience until I had a chance to discuss this further with QA. Our current theory is that something is causing Roon to re-draw a UI object multiple times and this is causing the slowness behavior.
We just released Roon build 538 a couple of hours ago, can you please upgrade to the newest build and let me know if you’re still seeing the same behavior there? I just want to check this aspect before going into deeper troubleshooting.
@mavmcl - It may or may not help, so I can’t make any promises, but I do want to see if there’s been any effect on the latest build before we dive into deeper troubleshooting, so please do let me know!