[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: kded4 eating CPU



Am Tuesday 05 April 2011 schrieb George Kiagiadakis:
> On Sat, Apr 2, 2011 at 10:57 PM, Sandro Weiser <sandro.weiser@gmx.de> 
wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA512
> > 
> > I have 2 kded4 processes after starting kde:
> > 
> > user      13274 79.5  0.8 691152 50216 ?        Sl   15:58 278:58
> > kdeinit4: kded4 [kdeinit]
> > 
> > 
> > user      23195  0.1  0.7 618484 43224 ?        Sl   21:30   0:01
> > kdeinit4: kded4 [kdeinit]
> > 
> > one is always at nearly 100% cpu. I've to kill it with -9.
> > 
> > Any hints what's wrong and what can I do against this issue?
> > 
> > Sandro
> 
> I bet the first one that is eating the cpu was from a previous session
> of KDE. You didn't boot directly into that KDE session, but you logged
> out and in again, right? If this is the case, I just reproduced it and
> I have already found the cause, but it's pretty difficult to find a
> solution.
> 
> In any case, because I'm not sure if this can be reproduced at will
> and I don't want to kill this stuck kded4 instance before I have
> collected all the information required to file a bug (and therefore I
> cannot retry), if anybody wishes to help me confirm it's the same bug
> we are all experiencing, next time this happens please do the
> following:
> 
> 1) Install gdb, libqt4-dbg and kdelibs5-dbg
> 2) Find the PID of the kded4 instance that eats CPU (for example, in
> the above output it's 13274)
> 3) Run "gdb --pid 13274" (where 13274 is the PID you found)
> 4) In the gdb command line run "thread apply all bt" and send me the
> output.

Now I got it. I reported a debian bug about it, to have it properly 
tracked.

kdelibs-bin: on logging out and in again kded4 (often?) loops on the CPU

Ciao,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

Attachment: signature.asc
Description: This is a digitally signed message part.


Reply to: