When I close Roon + Core on my Windows 10/Creator’s Update machine, the RAATServer and Roon processes stay in Task Manager for a few to several minutes until I either reboot or they finish whatever they are doing. I cannot kill the processes manually in Task Manager – the only option is to reboot or wait.
That means that if I need to close/re-open Roon + Core on my Windows box, it’s a multi-minute evolution and may be an indication that deeper stuff lies behind whatever behavior prompted me to close Roon in the first place.
Hi @Jeff_Bellune ---- Thank you for the report and sharing this observation with us. The feedback is appreciated.
To answer you question, “No”, this is not behavior we’d expect to be seeing. Can you confirm for me if you are making use of any antivirus applications on this Win10 machine?
(Sidebar: Ever since the big kerfuffle worldwide about ransomware, Webroot has been really aggressive about letting new or updated known software access the Internet. After 2 minutes when a program is launched and subsequently challenged by Webroot, it will default to allowing the connection, but the user can override the timer and future alerts by forcing an “Allow Always” operation. Roon and RAATServer have Allow Always trust normally and as soon as possible after an update. Allow Always is in effect for the latest version of webroot, and my issue is after exit, not during launch.)
When these Roon processes continue to appear in Task Manager, do you see any ongoing CPU use, I/O activity, etc?
You might try investigating with some tools from SysInternals (part of Microsoft). Download the suite. I’d then start with, say, DiskMon, Disk Usage, Handle, Process Explorer, Process Monitor; other possibilities are Sysmon, TCPVIew and WinObj.
No. The memory allocated stays allocated, and the CPU usage stays at zero. At least until the process quits on its own, which sometimes does happen, when the CPU usage goes to 1%.
If there’s no CPU use and no I/O activity, the most likely explanation is that a thread in the process is waiting for something (and it could be a DLL waiting; Process Explorer might be of use here). The Roon development people may have some ideas.
Hi @Jeff_Bellune ---- Thank you for following up with me and providing the requested materials.
At first glance it looks like I have everything I need but if additionally materials are needed I will be sure to let you know. We greatly appreciate your patience while our team conducts their evaluation. Once I have some feedback I will be sure to update this thread promptly.
Hi @Jeff_Bellune ----- Thank you for your patience while our techs have been looking into this issue you’ve reported to us. It is very appreciated!
Moving forward, the team is having a hard time pinpointing the cause of this behavior you’re experiencing and right now the working theory is that this could still be linked to the “Webroot” application.
While I understand that you’ve tested with it disabled, the team suggests uninstalling it completely and confirming if you make the same observations with process still being active in the task manager.
I uninstalled webroot completely (no easy task), rebooted, and the issue remains. If anything, it’s gotten worse. I tried to add Ten Years After’s A Space In Time from TIDAL into my library, and the last 2 songs came in as duplicates: each track appeared twice as part of a work with the same name. Re-Analyzing and Re-Identifying and Re-Scanning had no effect. When I closed Roon in hopes that restarting it would remove the duplicate tracks + work display, the Roon process took even longer to disappear from Task Manager than it usually does.
The time of closing Roon was apporximately 1640. I will PM you with the logs from this session. I have not restarted Roon since the TYA incident.
Hi @Jeff_Bellune ---- Thank you for touching base with me and giving the proposed test a shot, I am sorry to hear that it did not yield a more positive result.
I considered performing a full reset of Windows 10 to see if I could get this issue to go away. However, my schedule didn’t allow me the 3-4 days of down time I would need to fully reinstall all my programs and plugins, so I didn’t reset Windows.
As of Roon version 1.3 (Build 262), I no longer have this issue. So whether it was recent Windows updates, recent Roon updates, or both, the issue is solved for me.
This fits in well with my personal philosophy of: “if you ignore a problem long enough, it will go away”.
, can you please verify how you are closing the application once you are done with your listening session(s)?
