Hi @noris
The latest release still hasn’t resolved the issue with my large database of music. My WCore/Roon still has the pulsing orb with no functionality. What i did notice in a moment of functionality is that at one point Roon had scanned over 1.6 million files only to be showing a new scan of about 200 thousand. So it lost the previous scan.just weird.
It looks like you’re getting out of memory crashes due to the size of your library being more than 8GB of RAM can handle. If the number of tracks being scanned doesn’t match what you expect Roon could be scanning junk.
Hi Daniel,
Thanks for reaching out to me. I have 16 GB of ram installed. I don’t know if that should be enough.
Can someone review my logs? I’m currently running with a disabled drive, that’s the offender. How would I know if it’s junk?
That should be fine for a library the size of yours as long as you aren’t using a lot of DSP options. We will investigate your logs.
Hey @Watchdog507 ,
Your Roon Server is reporting as having 8GB of RAM according to logs (RAM : 7869MB), not 16 GB.
Can you share a screenshot of your Roon Settings → Storage page? Do you have the entire drive added as a storage location? Are you also using that drive to store your Roon backups to it?
Here’s the screenshot. I’ve disabled the offending drive to use Roon. I’ve not configured backups until the system is stable.
According to your logs previously you had backups saved to a subfolder in your library folder. This means every time a backup was made it triggered Roon to rescan again. If you move backups out of that folder the CPU cycles should calm down.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
