threads choke up system after shutdown of amarok

Board index

Page 1 of 1 (5 posts)

Tags:

Martijn van Eenennaam Registered Member Posts 5 Karma 0	threads choke up system after shutdown of amarok Mon May 30, 2005 11:30 pm Hello, After I close amaroK (with top open on my other monitor) I see that a lot of amarokapp processes get started, choking up the entire system. Nothing reacts, even the mousepointer does not move anymore! It reminded me of a **** in my windows-days Does anyone have any idea why it does this? Could it be because I have nearly 30,000 mp3\'s in my collection, mounted over NFS? Thanks for any helpful hints.
mortiferus Registered Member Posts 74 Karma 0	Re:threads choke up system after shutdown of amaro Tue May 31, 2005 4:38 am I am sorry that I cant help you, just wanted to mention that my collection is 23000 tracks mountet over NFS. It is even a slow NFS connection, and I dont experience your problems. Try another playback engine (the general response to every problem:P)
Hans Administrator Posts 3304 Karma 24 OS	Re:threads choke up system after shutdown of amaro Tue May 31, 2005 8:07 pm Which version? A SVN version did this to me as well, but it was fixed fast. Problem solved? Please click on "Accept this answer" below the post with the best answer to mark your topic as solved. 10 things you might want to do in KDE \| Open menu with Super key \| Mouse shortcuts
Martijn van Eenennaam Registered Member Posts 5 Karma 0	Re:threads choke up system after shutdown of amaro Wed Jun 01, 2005 2:41 am I am using the Xine engine. I have manually removed the collection.db and added files album by album, i figured there could be a corrupt mp3 or something. I\'ll try to get some debug output, thanks for your help so far.
Martijn van Eenennaam Registered Member Posts 5 Karma 0	Re:threads choke up system after shutdown of amaro Tue Jun 07, 2005 8:25 pm It looks like some kind of operation on the database does not really succeed, and every thread after that which tries to access the database cannot get to it. It does this every couple of songs. It does stop with a CTRL-C but ofcourse that is no real solution... amarok: [CollectionDB] [ERROR!] Busy-counter has reached maximum. Aborting this sql statement! amarok: [CollectionDB] [ERROR!] [virtual QStringList SqliteConnection::query(const QString&)] sqlite_step error. amarok: [CollectionDB] [ERROR!] database is locked amarok: [CollectionDB] [ERROR!] on query: SELECT DISTINCT artist.name FROM tags,artist,album WHERE 1 AND tags.sampler = 1 AND album.id=tags.album AND artist.id=tags.artist LIMIT 0, 1 amarok: [CollectionDB] sqlite3_step: BUSY counter: 13 amarok: [CollectionDB] sqlite3_step: BUSY counter: 1 amarok: [CollectionDB] sqlite3_step: BUSY counter: 14 amarok: [CollectionDB] sqlite3_step: BUSY counter: 2 amarok: [CollectionDB] sqlite3_step: BUSY counter: 15 amarok: [CollectionDB] sqlite3_step: BUSY counter: 3 amarok: [CollectionDB] sqlite3_step: BUSY counter: 16 amarok: [CollectionDB] sqlite3_step: BUSY counter: 4 amarok: [CollectionDB] sqlite3_step: BUSY counter: 17 amarok: [CollectionDB] sqlite3_step: BUSY counter: 5 amarok: [CollectionDB] sqlite3_step: BUSY counter: 18 amarok: [CollectionDB] sqlite3_step: BUSY counter: 6 amarok: [CollectionDB] sqlite3_step: BUSY counter: 19 amarok: [CollectionDB] sqlite3_step: BUSY counter: 7 amarok: [CollectionDB] sqlite3_step: BUSY counter: 20 amarok: [CollectionDB] sqlite3_step: BUSY counter: 8 amarok: [CollectionDB] sqlite3_step: BUSY counter: 21