Summary: | kded4 high cpu load(50%) | ||
---|---|---|---|
Product: | [I don't know] kde | Reporter: | Cosmin <costexx> |
Component: | general | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | alexey.misc, faure, zahl |
Priority: | NOR | ||
Version: | 4.2.2 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Cosmin
2009-05-20 21:27:34 UTC
What does top say? This is most likely from the X server or graphics card drivers or something. Otherwise, we need some actual profiling information. There are general speed-ups between your version and 4.3beta. Hello! I've just installed kde 4.2.3 from debian-desktop.org. salmin@salmin:~$ sudo strace -p `pidof kded4` 2>&1 | head Process 19456 attached - interrupt to quit read(8, 0x6d5cb4, 4096) = -1 EAGAIN (Resource temporarily unavailable) poll([{fd=3, events=POLLIN}, {fd=8, events=POLLIN}, {fd=5, events=POLLIN}, {fd=9, events=POLLIN}, {fd=11, events=POLLIN}], 5, 0) = 0 (Timeout) read(8, 0x6d5cb4, 4096) = -1 EAGAIN (Resource temporarily unavailable) read(8, 0x6d5cb4, 4096) = -1 EAGAIN (Resource temporarily unavailable) poll([{fd=3, events=POLLIN}, {fd=8, events=POLLIN}, {fd=5, events=POLLIN}, {fd=9, events=POLLIN}, {fd=11, events=POLLIN}], 5, 0) = 0 (Timeout) read(8, 0x6d5cb4, 4096) = -1 EAGAIN (Resource temporarily unavailable) read(8, 0x6d5cb4, 4096) = -1 EAGAIN (Resource temporarily unavailable) poll([{fd=3, events=POLLIN}, {fd=8, events=POLLIN}, {fd=5, events=POLLIN}, {fd=9, events=POLLIN}, {fd=11, events=POLLIN}], 5, 0) = 0 (Timeout) read(8, 0x6d5cb4, 4096) = -1 EAGAIN (Resource temporarily unavailable) The kded4 process is loading cpu to 100%. If it's important I can add some information about fd salmin:/proc/19456/fd# ls -l 8 lrwx------ 1 salmin salmin 64 Май 22 22:00 8 -> socket:[15602558] salmin:/proc/19456/fd# netstat -p | grep 15602558 unix 3 [ ] STREAM CONNECTED 15602558 19456/kded4 *** This bug has been marked as a duplicate of bug 178228 *** |