Summary: | kde4d eats one CPU core | ||
---|---|---|---|
Product: | [Frameworks and Libraries] kdelibs | Reporter: | Toralf Förster <toralf.foerster> |
Component: | kded | Assignee: | David Faure <faure> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | lamarque, stephan.diestelhorst |
Priority: | NOR | ||
Version: | 0.1 | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
gdb output
gdb output gdb output gdb output |
Created attachment 58170 [details]
gdb output
Created attachment 58171 [details]
gdb output
Created attachment 58172 [details]
gdb output
*** This bug has been marked as a duplicate of bug 178228 *** (In reply to comment #4) > > *** This bug has been marked as a duplicate of bug 178228 *** Sure, ?! That mentioned bug was solved 1 year ago per SVN commit - but still happened in KDE 4.6.1 ! Bug 178228 is still open, your backtrace is similar to its, so the duplicate. |
Created attachment 58169 [details] gdb output Version: 0.1 (using KDE 4.6.1) OS: Linux Today I had again the situation where kde4d uses up to 50% of my dual-core processor. The process list gave : kded4(7106,tfoerste)─┬─{kded4}(7114) └─{kded4}(7122) I attached gdb to 7106 and killed the child process 122, howevere few minutes later the situation was the same. ThenI killed again a child, and finally I run a "kill -9 7106" the appropriate outputs of gdb are attached. I attach the output of "gdb 2>&1 | tee -a gdbX.log" onto this bug report. Reproducible: Didn't try OS: Linux (i686) release 2.6.38 Compiler: i686-pc-linux-gnu-gcc