Version: 2.1.1 (using KDE 3.3.1, SuSE) Compiler: gcc version 3.3.3 (SuSE Linux) OS: Linux (i686) release 2.6.5-7.108-default When Juk reaches the end of its playlist, the memory usage of the process balloons. As a result the system basically gets unusable, and the only way out is to kill juk. Note: while playing, memory usage is normal. Moreover, the problem doesn't occur when stopping play using the stop button. It only happens when playing stops because the end of the play list has been reached. This seems to be new in 3.3.1. In 3.3.0, everything behaved normally.
[cough] Thanks for checking for duplicates. This is only the 12th time this has been reported. ;-) *** This bug has been marked as a duplicate of 91467 ***
On Monday 01 November 2004 19:44, Scott Wheeler wrote: > ------- You are receiving this mail because: ------- > You reported the bug, or are watching the reporter. > > http://bugs.kde.org/show_bug.cgi?id=92539 > wheeler kde org changed: > > What |Removed |Added > --------------------------------------------------------------------------- >- Status|UNCONFIRMED |RESOLVED > Resolution| |DUPLICATE > > > > ------- Additional Comments From wheeler kde org 2004-11-01 19:44 ------- > [cough] Thanks for checking for duplicates. This is only the 12th time > this has been reported. ;-) > > *** This bug has been marked as a duplicate of 91467 *** Oops, sorry for that. Is there a workaround available (such as downgrading to kde-3.3.0)? Unfortunately, I've wiped my 3.3.0 rpm's before I noticed the problem, and interestingly enough, neither kde.org nor the mirrors carry them any longer... Any ideas? Thanks, Alain
Yes, this wasn't broken in 3.3.0 and it's already fixed in what will be 3.3.2. Downgrading to 3.3.0 or waiting for 3.3.2 would both work, of of course grabbing the version from CVS.
On Monday 01 November 2004 22:49, Scott Wheeler wrote: > Yes, this wasn't broken in 3.3.0 and it's already fixed in what will be > 3.3.2. Downgrading to 3.3.0 or waiting for 3.3.2 would both work, of of > course grabbing the version from CVS. Thanks... but apparently 3.3.0 for SuSE is nowhere to be found (at least not at the usual places: ftp.kde.org:/pub/kde/stable/3.3 has no SuSE directory any more). Or I can wait for 3.3.2, when will it be ready approximatively? Any ideas? Thanks, Alain
On Monday 01 November 2004 23:13, Alain Knaff wrote: > Thanks... but apparently 3.3.0 for SuSE is nowhere to be found (at > least not at the usual places: ftp.kde.org:/pub/kde/stable/3.3 has no > SuSE directory any more). That's up to SuSE -- you might poke around on their site. > Or I can wait for 3.3.2, when will it be ready approximatively? The bug fix releases are usually 4-6 weeks apart. So roughly 1-3 weeks.