Version: 1.4-SVN (using KDE KDE 3.5.2) Installed from: SuSE RPMs Ok, here are the steps to reproduce: 0. you need a _large_ collection 1. open collectionbrowser, select all tracks 2. right-click to open the context menu of the selected tracks result: amaroK hangs for about 20 minutes for me (takes 100% cpu), memory usage goes up. After that time it continues as normal (shows context menu) expected result: show context menu after... well, a few seconds? The usual stuff: xine-engine, sqlite (I know sqlite with large collections... but this way you find bugs ;-) The hang with large CPU usage: Dangle things this is due to the context menu entry "Edit metainformation of N tracks", where N is the number of selected tracks. counting them takes some time. If this is correct I suggest the following solution: Limit N. if (N > 500) (or whatever numer) then only display "edit metadata of selected tracks", else display "Edit metainformation of N tracks". Growing memory: According to pmap memory usage goes up from 117792K to 140396K, so amarok seems to lose 22604K. The collection has a size of 52607 tracks, so that is nearly 0.5K per track. I can attach the pmap and if needed try to create a valgrind-log for this issue.
Now, the slowness is due to enumerating the urls of all selected items, which involves many sql queries.
This bug is still present in 1.4.9.1 although it is not present in 2.x and the context menu appears instantly for a selection of ~7000 tracks.
Thanks Matt. Let's consider it fixed then.