[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    Bug#24244: Various KDE applications start using 99.99% CPU  time...
From:       "Jesper Juhl <juhl () eisenstein ! dk>" <juhl () eisenstein ! dk>
Date:       2001-04-17 8:41:11
[Download RAW message or body]


Sure, I'll try to get a 'strace' and a gdb backtrace the next time it
happens...

/Jesper Juhl



On Mon, 16 Apr 2001, Waldo Bastian wrote:

> Interesting problem. Can you, when it happens again, attach "strace" to one
> of the processes with 99% cpu> E.g. with
> 	strace -tt -p  <pid_of_process>
>
> And if possible, can you also attach gdb to one of the processes and make a
> backtrace? E.g. with
> 	gdb kdeinit <pid_of_process>
> and then
> 	bt
>
> Cheers,
> Waldo
>
> On Monday 16 April 2001 14:37, you wrote:
> > Package: kdeinit
> > Version: KDE 2.1.0
> > Severity: normal
> > Installed from:    Compiled From Sources
> > Compiler:          gcc v2.95.2
> > OS:                Linux
> > OS/Compiler notes: OS: Customized Slackware Linux 7.1
> >
> >
> > I have seen this several times; when I've been using KDE for a good number
> > of hours (usually 4-8) then suddenly the system starts to swap heavily and
> > everything slows down extremely. This can start while I'm reading a website
> > in Konqueror, viewing a .pdf document in xpdf or doing basically anything
> > (it can even happen while the system's not in use and is just standing
> > idle), but it never happens before after a good many hours of normal use.
> > At first I thought that it was some crond job kicking in, but no jobs
> > seemed to be running (just to be sure I turned off all crond jobs about a
> > week ago)... When I looked into it a bit more, I noticed that several
> > processes where taking up 99.99% CPU time (most of those are usually stuff
> > started by kdeinit). The massive swapping and high CPU load usually goes on
> > for about 5-10 minutes and then just disappear - only to reappear some 4-8
> > hours later.
> >
> > Last time this happened I started up kpm and the gimp and took a screenshot
> > of the kpm window to have a snapshot of the situation I could report here.
> > Bellow are the most interresting numbers from that screenshot (image
> > available upon request).
> >
> > %CPU  %MEM TIME CMDLINE
> > -------------------------
> > 99.99   1.24   1.98s  knotify
> > 99.99   3.26     0:21  kdeinit: kwin
> > 99.99   5.84     0:35  kdeinit: kicker
> > 99.99   1.38     0:11  kdeinit: klipper -icon klipper
> > 99.99  39.61  57:53  kdeinit: konqueror --silent
> > 99.99   4.80   3.62s  kpm -icon kpm -miniicon kpm
> > 99.99   3.57   0.16s /usr/lib/gimp/1.0/plug-ins/screenshot  0.00    0.00
> > 0.10s  (startkde) 0.00    0.84  4.43s  kdeinit: dcopserver --nosid
> >
> > (and so on - the rest of the listing is normal)
> >
> > At this point the system had been up for 9 hours and 52 min.
> >
> > I have absolutely no explanation for this, but it only happens when I'm
> > using KDE (I've been using fvwm2 and OpenLook for a few weeks just to make
> > sure), and about two thirds of the apps taking up 99.99% CPU are always
> > started by kdeinit - so I guess it's probably some obscure KDE or QT bug...
> >
> > I hope this is helpfull :-)
> >
> > Best regards,
> > Jesper Juhl
> > juhl@eisenstein.dk
> >
> >
> > (Submitted via bugs.kde.org)
>
> --
> bastian@kde.org | SuSE Labs KDE Developer | bastian@suse.com
>

[prev in list] [next in list] [prev in thread] [next in thread]