You could also enable INFO logging for database.info
(Settings/Advanced/Logging) before re-running a scan with max memory
mode. That would give us some information about what's going on without
modifying the code. Do NOT set the log level to DEBUG, as this could
create a huge scanner.log!
Well, i am not that IT professionell, all the commands i use i found out
on google:-)
But if you´d give me step by step instructions, i would be pleased to
help.
Please try the above with memory set to max. Yes I know, it'll crash the
scanner. But that's what I'm looking for. Maybe if you could monitor the
memory usage when it's getting closer to the optimize stage (and I know
again, this asking much :-)).
--
Michael
_______________________________________________
Squeezecenter mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/squeezecenter
