Version: (using KDE 4.2.2) OS: FreeBSD Installed from: FreeBSD Ports I frequently find up to four processes kdeinit4 with high CPU usage. They hang the system, even clock in the panel stops. After I kill them KDE4 unfreezes until the next time kdeinit4 hangs.
Is there any chance to get attention to this isue? This is the most urgent issue ith KDE4 causing me to kill kdeinit4 about 5 times per day.
I'm also with this issue. Using KDE 4.2.4, Qt 4.5.1 and Kubuntu Jaunty. Not experiencing the freezes, but the high cpu usage is there. It seems pretty random. Sometimes is one, sometimes is more. It starts after hours or after minutes the last time. I don't know how debug this. Can anybody give a hint? Maybe how to find out who is launching this app?
Just some more info: Yeap. It happened again. Here are the output for "ps aux": USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND bruno 9288 97.2 0.4 40844 8548 ? R 16:20 0:39 kdeinit4: kio_http [kdeinit] http local:/tmp/ksocket-bruno/klauncherMT9372.slave-socket local:/tmp/ksocket-bruno/plasmarK9428.slave-socket
I guess KDE people don't really care. it has been almost a month and a half and no reaction at all.
@Yuri: > I guess KDE people don't really care. stop with the passive-aggressive sillyness. > it has been almost a month and a half and no reaction at all. that's because this report doesn't have much information and is filed against the _wrong component_. in the last 31 days we've closed 3080 reports while 3190 new ones were opened, so we tend to be fairly busy. reports filed against the wrong component often don't get attention as soon as reports with more detail, which affect more people and which are properly assigned. now, kdeinit4 is what starts other kde4 application (performance reasons for that). so the original report is precisely useless as it doesn't say _what_ is actually causing the issue. Bruno's investigation shows the real problem: kio_http. and now i can move this report to the right place. Bruno: thanks for looking into it more on your system. *** This bug has been marked as a duplicate of bug 182778 ***