I uploaded the library.db with all 45 playlists some minutes ago.
Scan is still running. But quite interesting observation already: the memory footprint was pretty stable - until the playlist FTS index started. Scanning the largest of them took a little over 15mins. Memory usage immediately increased by 300-400MB, where it stayed for the first 5-10mins. Then it jumped by another 5GB, steadily increasing until it used about 8.5GB more than before this playlist...
_______________________________________________ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
