Version: unknown (using 4.2.87 (KDE 4.2.87 (KDE 4.3 >= 20090519)), Mandriva Linux release 2010.0 (Cooker) for i586) Compiler: gcc OS: Linux (i686) release 2.6.29.3-desktop586-1mnb Since the latest plasma update the yaWP widget causes the CPU to run at 100%. Closing the widget does not cure the problem until a reboot. How to reproduce: 1. Add yaWP to desktop, at this stage there is no problem if default city is used. 2. Change default city, this causes CPU activity to rise to 100%. If you run TOP in Konsole you will see kio_http is running taking (on my system) about 65% of CPU. 3. Each time the default city is changed another incidence of kio_http starts up. Tasks: 149 total, 3 running, 146 sleeping, 0 stopped, 0 zombie Cpu(s): 90.7%us, 9.0%sy, 0.0%ni, 0.0%id, 0.0%wa, 0.3%hi, 0.0%si, 0.0%st Mem: 1025700k total, 824404k used, 201296k free, 40988k buffers Swap: 4088500k total, 0k used, 4088500k free, 440216k cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 5156 david 20 0 61924 10m 6580 R 34.8 1.0 5:01.22 kio_http 5147 david 20 0 61884 10m 6580 R 34.5 1.0 5:01.40 kio_http 2876 root 20 0 389m 76m 21m S 12.6 7.6 1:34.98 X 5113 david 20 0 241m 27m 19m S 5.6 2.7 0:53.90 kwin 5117 david 20 0 287m 47m 26m S 4.3 4.8 0:39.00 plasma-desktop 5119 david 20 0 162m 17m 13m S 2.3 1.8 0:17.74 knotify4 5472 david 20 0 95176 19m 13m S 2.0 1.9 0:04.35 konsole 5498 david 9 -11 95076 5676 4328 S 1.7 0.6 0:14.33 pulseaudio 5121 david 20 0 2568 1336 816 S 0.3 0.1 0:00.53 ksysguardd 5523 david 20 0 82528 12m 9396 S 0.3 1.3 0:00.36 klipper 6124 david 20 0 149m 38m 25m S 0.3 3.9 0:17.03 konqueror 1 root 20 0 1732 568 500 S 0.0 0.1 0:00.74 init 2 root 15 -5 0 0 0 S 0.0 0.0 0:00.01 kthreadd 3 root RT -5 0 0 0 S 0.0 0.0 0:00.00 migration/0 4 root 15 -5 0 0 0 S 0.0 0.0 0:00.08 ksoftirqd/0 5 root 15 -5 0 0 0 S 0.0 0.0 0:00.11 events/0 6 root 15 -5 0 0 0 S 0.0 0.0 0:00.00 work_on_cpu/0
"Closing the widget does not cure the problem until a reboot." Logging out and logging in again also clears it.
I wonder if that widgets uses https:// (I guess not), as it could have some relation with a current bug related to it.
yes, this is a kio_http issue, and yaWP is a third party plugin so if it wasn't a kio_http thing it wouldn't be something the plasma team would deal with anyways (it would be up to the yaWP people) *** This bug has been marked as a duplicate of bug 182778 ***