º[quote=“noris, post:67, topic:99508”]
you should be able to rename the current “Roon” folder to “Roon_empty_Db” or something similar and rename the “Roon_old” folder back to “Roon” to get access to your old database (do make sure to exit Roon first though)
[/quote]
That is good to know, was painful to use other software today.
Thanks @noris
Hi @mavmcl,
Thanks for the ping. I did speak to QA again regarding this behavior, but we haven’t been able to reproduce this issue in-house with the Macs we have for testing, so we are still trying to narrow down this issue to one aspect of the hardware. A few questions which may help clarify further:
If you get into this high GPU state and stop clicking and stay on just one screen in Roon, does the GPU usage go back down or does it remain near the max?
Let’s try to minimize the amount of screens that are accessed. If you navigate just between your Overview and Library -> Tracks tab for a bit, are you able to reproduce the issue?
I have serious heating and slowing problems on macbook 12 from the year 2105. I have the latest version of Catalina and the latest version of Roon installed.
Hi @noris
A/ it does remain at 99% the only way I can get it to work around it will be to minimize Roon, do cmd+w, as soon as I maximize Roon it will reach the 99% of GPU usage. Or to get out of the state cmd+q until the next time.
I will give it a try and reply back.
Thanks.
can you confirm you have 99% of GPU usage and share a screenshot?
welcome to the forum @DANIEL_PELLEGRINO
hey @noris here is the homework:
20.40 started testing trying to repro:
From 20.40 to 20.50 constantly clicked and scrolled between ¨Overview and Tracks¨, 10 minutes, can’t repro.
From 20.50 to 21.00 constantly clicked and scrolled between ¨Overview and Discover¨ menu. After 10 minutes or so can’t repro.
From 21.00 to around 21.08 clicked between ¨Overview and Albums¨ scrolled through the 3000+ albums I have for about 5 minutes without stopping. Can’t repro.
At 21.08 decided to record my steps and do a more realistic test:
cmd+q Roon > open the app > Overview > Discover > Click an album from there > clicked the album artist > that triggered the issue at 21.09:
Closed Roon.
Second repro: 21.11 > Overview > Discover > Selected an album > scroll in the album > clicked in the album artist > that triggered the issue at 21.11 > closed Roon.
Forgot the screenshot…
3rd repro 21.14: Overview > Discover > selected an Album > clicked the album artist > clicked another album from that artist > that triggered the issue at 21.14 > closed Roon.
7.
At this point decided to record it.
I have found it is super easy to reproduce it Please have a look:
21.41:
21.44:
Logs:
https://drive.google.com/file/d/1qKr3xqD9VRmmxBrfiXZlsF14pqoiA0aB/view?usp=sharing
Let me know if we need something else, I am always open to a Zoom session or so if needed.
Thanks @noris
Hi @mavmcl,
Thanks for the further attempts and for the videos!
I took a look over them and it looks like we’re onto something here, the high stuck GPU behavior happened exactly once you started flipping between the Composer and Performer tab.
We’ve started testing with this aspect in mind in the QA lab and we’ll take a look to see if we can reproduce your findings on the Mac’s we have in-house.
Thanks again for the testing you have done so far, I’ll let you know how our testing goes on our end but overall this is fantastic news as we now have reproductions steps!
Hi @noris thanks, nice the hear that, looks like you will need a MBP 16 inch 2019 or an 2019 iMac to repro.
Please keep me posted if you have news from QA or ir need further repro on my side.
Thanks.
Hi @noris I can tell it has turned for worst after last update to 537, before the update it happened every couple of days, nowadays it happens just after few minutes or clicks, I have to run Roon permanently minimized, a shame I bought this computer to have Roon running in fullscreen.
Thanks.
hi @noris I have been using my old MacBook Air 2014 today, installed the Roon interface then used it the whole afternoon, it is impressive the low resource usage in this machine, QA will not be able to reproduce the issue in an older Mac the will need a 2019 mbp or iMac.
Hi @mavmcl,
I wanted to touch base with some good news. We’ve managed to reproduce this issue on a staff member’s 2019 16" MBP and gathering all the necessary info for a ticket for the devs 
. If there’s any other info we need from your end we will let you know, thanks!
hi @noris those are great news!!! thanks for sharing, hope the devs can get our Roon fixed!!!
Great news!
Following. I am experiencing the same issues on my 2015 Macbook Pro.
Hi @mavmcl,
I have been discussing this issue with QA today, and we do have an update to share.
As I mentioned earlier in the thread, we were able to reproduce this issue, but we were only able to reproduce exactly once, it seems that no matter how much we’re trying to recreate the issue on multiple Macs in the lab, we’re not succeeding any longer, even on the 2019 MBP which exhibited it once.
I spoke to QA again and we’re still trying to narrow down the proper steps to troubleshoot this further. One aspect which may help with discovering the underlying cause would be a sample of the Roon process when your PC is in this state.
Can I please request that you @mavmcl, @jmvdv & @RustySanwa provide a sample of the Roon process when you’re in this state? Hopefully this will give further clues to narrow down what exactly is causing this issue.
Thanks all.
Hi @noris fair enough, let me finish up playing with a Qobuz issue and will collect the data you are requesting, have QA or the testers to use Roon in a secondary desktop in the Mac, it is easy to repro as well when in full screen.
Thanks!
Hey @noris here you go, it is just happening now, RAAT and Roon Samples link: https://drive.google.com/open?id=1VWuKU6huG39X8NOxAnX3PoaExJv4BGyp
