Version: (using KDE KDE 3.3.1) Installed from: Slackware Packages Compiler: gcc 3.3.4 OS: Linux KDE 3.3.1's juk suffers from various deadlocks happening at random or semi-random[0] way. One reproducable form of deadlock is happening when starting an empty juk. No mp3 files added nowhere (for example fresh kde start). If you double click in the empty space in the playlist window, juk raises 100% CPU usage and fills up all the memory and all the swap memory. The system is totally deadlocked (not even the mouse moving) and after a while luckily kernel kills juk and the system starts responding again. [0] Another form of deadlock happens like this: Imagine a "full" juk with mp3s loaded and playlists. One song is played on one of the playlists. Then I choose a different playlist and I either double click on a new song, or click next and the deadlock happens again. I said semi-random way for this one because I think it doesn't always happen.
*** This bug has been marked as a duplicate of 91467 ***