Threaded Mode | Linear Mode

pvanosta · 29-12-2015, 11:00

Looking at the log, the crash happens at the same point in the scan (when scanning the same set of files). Back to the drawing board...

simoncn · 29-12-2015, 13:44

Please follow all the steps from this post exactly as listed there. In order to help you solve this problem, I would like to see the log file that results from running with the resourceInfo property set to 1000.

pvanosta · 06-01-2016, 16:47

Thanks all. As I was troubleshooting this issue on my brother's Synology (DS412+) over the holidays, I wanted to see what happened on my system when I returned home. I have the DS 1513+ with 5 times 6TB in hybrid raid and a larger library than my brother. MinimServer installed without a hitch and scanned my entire library fairly quickly (191,000 tracks on 18,004 albums).

So it works for me.

simoncn · (This post was last modified: 06-01-2016 18:30 by simoncn.)

(06-01-2016 16:47)pvanosta Wrote: Thanks all. As I was troubleshooting this issue on my brother's Synology (DS412+) over the holidays, I wanted to see what happened on my system when I returned home. I have the DS 1513+ with 5 times 6TB in hybrid raid and a larger library than my brother. MinimServer installed without a hitch and scanned my entire library fairly quickly (191,000 tracks on 18,004 albums).

So it works for me.

I would still be interested to see the resourceInfo=1000 log from your brother's NAS if possible. It might be that his NAS has less RAM than yours and this is why the Java heap is running out of memory after less than 150,000 tracks. Another possibility is something in his library (or perhaps a MinimServer bug) that is consuming an unusually large amount of memory. The resourceInfo=1000 log should provide me with some clues to point me in the right direction.