| Summary: | 100% cpu reading from a non-existing unix socket | ||
|---|---|---|---|
| Product: | [Unmaintained] plasma4 | Reporter: | Costin Grigoras <costing> |
| Component: | general | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | aseigo, c.kurrat, dominik.tritscher, mail, satya461, sittingduck, tantalus1983, zmihaly |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
It seems to be caused by the "Calendar" widget. Without it the CPU usage is normal, but enabling it makes plasma go to 100% CPU. It's very easy to reproduce, happens every time you enable/disable it. This seems to be related to Bug 187699. What exactly do you mean with enabling/disabling? Do you place a calendar widget on the desktop or do you click on a clock widget to bring up the calendar? Adding and removing the calendar from the desktop causes the high cpu usage. Just opening it by clicking on the clock doesn't produce any extra load. I can confirm that plasma consumes a whole CPU and it just disappears if I remove the calendar widget. I have the same behaviour with one exception: I can add the calendar to my desktop an nothing happens. Only if i MOVE it, CPU goes high. So try, as a temporary workaround, placing this plasmoid at the right place when adding it. Confirmed (4.2.2 on Gentoo Linux ~x86). I could also reproduce the behaviour Alexander describes in Comment #5. I have the same behavior as described by Alexander (with 4.2.2 on Gentoo amd64), but locking the widgets has the same affect as moving the calendar widget. Installed Kubuntu 9.04 - facing the same issue when calendar plasmoid is used. Please change the status to CONFIRMED. so, nobody actually answered Dominik's question: are you dragging the calendar from the clock to the desktop, or are you adding the Calendar widget directly from the Add Widgets dialog? Adding the widget to the desktop directly, not dragging the clock. But I guess this should be fairly easy to reproduce, 30 seconds flat for both cases :) is anyone using 4.2.3, 4.2.4 or 4.3beta? this bug should have been fixed in 4.2.3 .. if you can upgrade and confirm, then this is a (fixed) duplicate of bug #187699 I have 4.3beta2 running and there is no high cpu load when having a calendar widget on the desktop. I think this can be closed, it has been fixed. I installed 4.3.1 today from ubuntu's launchpad-ppa http://ppa.launchpad.net/kubuntu-ppa/backports/ubuntu. I have high CPU load from plasma - cause unknown, no work-around, except for renice 20 -p `pidof plasma` I removed every single item from the plasma bar so that it is just a blank bar, and I am still in vacuum cleaner mode. Plasma is doing select, writev(3,...), select(), read(3,...) thre times, a total of 387616 bytes, and then read returns EAGAIN. I'll bet there is nothing wrong with the plugins -- there is something wrong with the handling of EAGAIN -- when you get EAGAIN, you're not supposed to repeat your request, but simply wait a little bit, and then read again. |
Version: (using KDE 4.2.2) OS: Linux Installed from: Ubuntu Packages Infinite loop doing this: $ ps auwx | grep plasma costing 6469 92.3 2.2 291696 47276 ? Rl 10:08 8:20 /usr/bin/plasma $ strace -p 6469 ............ read(3, 0x998e474, 4096) = -1 EAGAIN (Resource temporarily unavailable) poll([{fd=4, events=POLLIN}, {fd=10, events=POLLIN}, {fd=3, events=POLLIN}, {fd=6, events=POLLIN}, {fd=11, events=POLLIN}, {fd=13, events=POLLIN}, {fd=20, events=POLLIN}, {fd=24,events=POLLIN}, {fd=26, events=POLLIN}], 9, 0) = 0 read(3, 0x998e474, 4096) = -1 EAGAIN (Resource temporarily unavailable) clock_gettime(CLOCK_MONOTONIC, {568, 412999033}) = 0 clock_gettime(CLOCK_MONOTONIC, {568, 413097499}) = 0 clock_gettime(CLOCK_MONOTONIC, {568, 413169090}) = 0 read(3, 0x998e474, 4096) = -1 EAGAIN (Resource temporarily unavailable) poll([{fd=4, events=POLLIN}, {fd=10, events=POLLIN}, {fd=3, events=POLLIN}, {fd=6, events=POLLIN}, {fd=11, events=POLLIN}, {fd=13, events=POLLIN}, {fd=20, events=POLLIN}, {fd=24,events=POLLIN}, {fd=26, events=POLLIN}], 9, 0) = 0 read(3, 0x998e474, 4096) = -1 EAGAIN (Resource temporarily unavailable) clock_gettime(CLOCK_MONOTONIC, {568, 413602419}) = 0 clock_gettime(CLOCK_MONOTONIC, {568, 413715409}) = 0 clock_gettime(CLOCK_MONOTONIC, {568, 413805033}) = 0 read(3, "\34\353l:\2\0\340\2\31\1\0\0]\254\10\0\0\330\202\277\312"..., 4096) = 32 read(3, 0x998e474, 4096) = -1 EAGAIN (Resource temporarily unavailable) .............. This is the socket: ls -l /proc/6469/fd/3 lrwx------ 1 costing costing 64 2009-04-03 10:18 /proc/6469/fd/3 -> socket:[19319] However I cannot find the number in any way: $ sudo netstat -apn | grep 19319 unix 3 [ ] STREAM CONNECTED 19319 6469/plasma $ sudo lsof | grep 19319 plasma 6469 costing 3u unix 0xf55a5200 19319 socket $ sudo lsof | grep 0xf55a5200 plasma 6469 costing 3u unix 0xf55a5200 19319 socket