Ok a weird thing has been happening sometimes in amarok (SVN updated today). It seems to be triggered if I add a few songs to the playlist (usaully when I right click to add a whole album) then it does the automatic collection scan. The Collection becomes empty and the computer gets so slow (I have a p4 2. I can\'t do anything and have to reboot. Ummm I don\'t know what to say or do cuz there was no crash report but I\'d be glad to help out anyway I can to get this fixed.

Do a `make clean` and reinstall if you haven\'t already and try again. Maybe be ready to SSH from another computer so that you don\'t have to do a hard reboot in case it reboots. You might as well follow the directions on the FAQ to try and obtain a backtrace as well.

Ok

It was doing this in the console window before it crashed:

amarok: [CollectionDB] [ERROR!] Busy-counter has reached maximum. Aborting this sql statement!
amarok: [CollectionDB] [ERROR!] [virtual int SqliteConnection::insert(const QString&, const QString&)] sqlite_step error.
amarok: [CollectionDB] [ERROR!] database is locked
amarok: [CollectionDB] [ERROR!] on insert: INSERT INTO related_artists ( artist, suggestion, changedate ) VALUES ( \'Mullmuzzler\', \'Enchant\', 0 );
amarok: [CollectionDB] sqlite3_step: BUSY counter: 1
amarok: [CollectionDB] sqlite3_step: BUSY counter: 2
amarok: [CollectionDB] sqlite3_step: BUSY counter: 3
amarok: [CollectionDB] sqlite3_step: BUSY counter: 4
amarok: [CollectionDB] sqlite3_step: BUSY counter: 5
amarok: [CollectionDB] sqlite3_step: BUSY counter: 6
amarok: [CollectionDB] sqlite3_step: BUSY counter: 7
amarok: [CollectionDB] sqlite3_step: BUSY counter: 8
amarok: [CollectionDB] sqlite3_step: BUSY counter: 9
amarok: [CollectionDB] sqlite3_step: BUSY counter: 10
amarok: [CollectionDB] sqlite3_step: BUSY counter: 11
amarok: [CollectionDB] sqlite3_step: BUSY counter: 12
amarok: [CollectionDB] sqlite3_step: BUSY counter: 13
amarok: [CollectionDB] sqlite3_step: BUSY counter: 14
amarok: [CollectionDB] sqlite3_step: BUSY counter: 15
amarok: [CollectionDB] sqlite3_step: BUSY counter: 16
amarok: [CollectionDB] sqlite3_step: BUSY counter: 17
amarok: [CollectionDB] sqlite3_step: BUSY counter: 18
amarok: [CollectionDB] sqlite3_step: BUSY counter: 19
amarok: [CollectionDB] sqlite3_step: BUSY counter: 20
amarok: [CollectionDB] sqlite3_step: BUSY counter: 21
amarok: [CollectionDB] [ERROR!] Busy-counter has reached

then the backtrace after gdb stopped it:

#0 0x41b013e1 in select () from /lib/libc.so.6
#1 0x41594a18 in ?? () from /usr/lib/qt/lib/libqt-mt.so.3
#2 0x0000001a in ?? ()
#3 0x4111fd08 in QEventLoop::enterLoop () from /usr/lib/qt/lib/libqt-mt.so.3
#4 0x4111fbb8 in QEventLoop::exec () from /usr/lib/qt/lib/libqt-mt.so.3
#5 0x4110dba1 in QApplication::exec () from /usr/lib/qt/lib/libqt-mt.so.3
#6 0x0817eaeb in main (argc=1, argv=0xbffff5e4) at main.cpp:89

hope this helps

If any developer wishes to reply that\'d be great, oh and I\'m using the xine engine at the time.

It took me a while but I actually prefer Amarok over Juk but Juk seems to be more stable so I\'m looking forward to Amarok in the future

Hi Shawn I am having the same problem, also using xine.

I don\'t know what causes this, could be the sqlite? I have had it with my entire (30k mp3\'s) collection but also with a few hundred it does this.

I don\'t know what causes this,

But perhaps now I have an idea, the database for some reason remains locked, and the program cannot access it anymore.

amarok: [CollectionDB] [ERROR!] database is locked
amarok: [CollectionDB] [ERROR!] on insert: INSERT INTO related_artists ( artist, suggestion, changedate ) VALUES ( \'Moonspell\', \'Iced Earth\', 0 );

Which leads me to believe there is a (serious?) deadlock problem.

The music keeps playing, but errors keep on rolling on the Konsole. It has been trying to INSERT for over ten minutes now and it just keeps on going.

Two options:
- carefully return every lock after completion
- make timeout on INSERT. if (unable_to_get_lock) after 50 tries then fail.

Oh wait it just stopped giving error messages, the music is playing but the rest hangs...

I\'ve been having almost the same problem with my system running amarok 1.3-svn, it keeps trying to rebuild my collection from scratch about every 10 minutes with the \"build collection\" button in the context browser (usually goes away back to normal in a few minutes), and once in a while this leads to a crash of either amarok, or in one case my entire system, requiring a reboot. The first time the crash happened i did have a mail pop up with a back trace, and i\'ve sent that along. i\'ve followed suggestions in the #amarok channel to delete my sqlite database as well as my amarokrc, with no luck. I plan on updating from the svn and switching to mysql soon to see if it\'s an issue with sqlite.

Yep, I switched over to mysql today and so far so good, it built it\'s collection once and has been running nice and fast for a few hours now.