> > Hmm, nothing interesting here, the slowest query is 0.2s if I understand it > correctly, to 20-30 s delays. You say the Amarok event loop stops for that > extended periods of time. Could you please: > > 1. Install debugging symbols for Amarok, kdelibs, qt, glibc, glib > 2. Run Amarok grom gdb: `gdb --ex run --args amarok --debug --nofork` > 3. Trigger the temporary freeze > 4. Hit Ctrl+C in gdb, > `(gdb) thread apply all bt 30` <- save entire backtrace > `(gdb) cont` <- resumes normal Amarok operation > > Please repeat Ctrl+C -> backtrace -> cont cycle several times and look if the > backtrace of Thread 1 looks similar each time. If so, please file a bug about > it, copy the full backtrace and CC me on the bug. >
I did what you instructed and opened this ticket. https://bugs.kde.org/show_bug.cgi?id=301700 Let me know if I can be of further assistance. _______________________________________________ Amarok mailing list Amarok@kde.org https://mail.kde.org/mailman/listinfo/amarok
