Version: 2.1-SVN (using 4.2.64 (KDE 4.2.64 (KDE 4.3 >= 20090218)), Gentoo) Compiler: x86_64-pc-linux-gnu-gcc OS: Linux (x86_64) release 2.6.26-tuxonice hi, i noticed that amarok becomes a real memory hog when "watch collection for changes" is enabled and there is some regular file activity (creation) in a monitored directory - even if the files are not playable files the memory footprint still grows. after a few hours amarok is blown up to 1,2 GB, no fun then.
debug output during scan is quite normal, happens also with no files changed, can anyone confirm this? (i used ksysguard) amarok: BEGIN: void ScanManager::startIncrementalScan() amarok: BEGIN: QStringList ScanManager::getDirsToScan() amarok: END__: QStringList ScanManager::getDirsToScan() - Took 0.73s amarok: GOING TO SCAN: amarok: Scanning nothing, return. amarok: BEGIN: void ScanManager::writeBatchIncrementalInfoFile() amarok: END__: void ScanManager::writeBatchIncrementalInfoFile() - Took 0.95s amarok: END__: void ScanManager::startIncrementalScan() - Took 1.7s
We will probably have to use the Valgrind memory debugging tool to diagnose this leakage properly. It should be able to detect the leak.
At startup Amarok 2.1svn takes about 100 MB of RAM, which I think is OK for my big music collection (~35000 files). But after running Amarok for one or two days the RAM usage increases to 1 GB. It increases RAM usage, even if nothing is played. Every hour it adds about 25 MB.
i can confirm this behaviour with a similar sized collection. the collection scanner keeps scanning even though nothing has been added to the (sub-)directories.. when 'watch folders' is disabled, the update colletion takes much too long as well and while scanning the cpu usage goes up to 100%.
This should have been fixed about a week ago. Please try recent SVN.
Yes, works here.