If I add a bunch of folders (probably 15 gigs worth) of music, after a bit of playing, Amarok starts paging the harddrive to the point where it slows KDE down to where I can barely kill amarok. This is with a cvs download from last night.

So I ran it in gdb (I know nothing else to use) and this appears to be where it is getting stuck. I think. After 4 minutes of running the program, I still couldn't interact with it. So I killed it, but not before I got a back trace. Let me know if this helps.

[code:1]
#0 0x00f30b24 in posix_memalign () from /usr/lib/libkdecore.so.4
#1 0x00f2fd99 in posix_memalign () from /usr/lib/libkdecore.so.4
#2 0x00f2f286 in malloc () from /usr/lib/libkdecore.so.4
#3 0x044743ae in operator new () from /usr/lib/libstdc++.so.5
#4 0x044744df in operator new[] () from /usr/lib/libstdc++.so.5
#5 0x014cd42d in QString::latin1ToUnicode () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#6 0x014cddc8 in QString::QString () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#7 0x0808fd8e in CollectionDB::execSql (this=0x9010738, statement=@0xfeedf2c0, values=0xfeedf340, names=0x0, debug=false)
at collectiondb.cpp:611
#8 0x080921d5 in CollectionDB::scanModifiedDirs (this=0x9010738, recursively=true, importPlaylists=true) at collectiondb.cpp:859
#9 0x080874cd in CollectionView::scanMonitor (this=0x900b788) at collectionbrowser.cpp:308
#10 0x08088f84 in CollectionView::timerEvent (this=0x900b788) at collectionbrowser.cpp:612
#11 0x011f7d03 in QObject::event () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#12 0x012304ef in QWidget::event () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#13 0x00bea372 in KListView::event () from /usr/lib/libkdeui.so.4
#14 0x0119dfaf in QApplication::internalNotify () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#15 0x0119d5ae in QApplication::notify () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#16 0x00e01223 in KApplication::notify () from /usr/lib/libkdecore.so.4
#17 0x0118d895 in QEventLoop::activateTimers () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#18 0x01147efb in QEventLoop::processEvents () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#19 0x011b01f8 in QEventLoop::enterLoop () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#20 0x011b00a8 in QEventLoop::exec () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#21 0x0119e201 in QApplication::exec () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#22 0x0811311c in main (argc=1, argv=0xfeedfba4) at main.cpp:66


(gdb) up 8
#8 0x080921d5 in CollectionDB::scanModifiedDirs (this=0x9010738, recursively=true, importPlaylists=true) at collectiondb.cpp:859
859 execSql( command, &values );
(
(gdb) p *this
$7 = {<> = {}, static metaObj = 0x8e7fbd0, m_amazonLicense = {static null = {
static null = , d = 0x8c6cf78, static shared_null = 0x8c6cf78}, d = 0x8c6cf78,
static shared_null = 0x8c6cf78}, m_db = 0x9014768, m_weaver = 0x9016c48, m_monitor = 80, m_cacheDir = ,
m_coverDir = }
[/code:1]

Further confirmation that the problem is in the collection update:

Have been running, closing and opening amarok with the monitor changes feature disabled, and have not had any issues. I can simply update and it does this with no problems.