Version: unknown (using KDE 3.2.0, compiled sources) Compiler: gcc version 3.3.2 (Debian) OS: Linux (i686) release 2.6.1dell-optiplex Quite often I have a load of 12 or 20 or so after browsing some sites I regularly visit. This is always due to various kio-http processes eating all my processor time. I've been seeing this for about a month now (I'm running BRANCH currently) but never found out which site causes this.. Any help in finding out what caused these to hang? For example; which URL they are trying to fetch?
See kdebase/kioslave/DEBUG.howto for how to redirect kio_http debug output to /tmp/http. Then, when you have hanging processes, you can lookup the PIDs in /tmp/http and see which URL it was last used for. (And what the last activity was)
I got this one yesterday: Hang occurred three times at www.duden.de, 3_2_BRANCH from 24.02.2004 konqueror: KonqView::setLocationBarURL http://bugs.kde.org/show_bug.cgi?id=53629 this=0x81e6f58 konqueror: KonqMainWindow::setLocationBarURL: url = http://bugs.kde.org/show_bug.cgi?id=53629 kparts: 0x80cbb48 emitting activePartChanged 0x82e1bd8 konqueror: Part is already active! konqueror: KonqMainWindow::slotPartActivated 0x82e1bd8 khtml konqueror: New current view 0x83be108 kparts: MainWindow::createGUI, part=0x82e1bd8 KHTMLPart kparts: deactivating GUI for 0x81e6840 KHTMLPart konqueror: KonqView::setLocationBarURL http://www.duden.de/ this=0x83be108 konqueror: KonqMainWindow::setLocationBarURL: url = http://www.duden.de/ kparts: 0x83d35d0 emitting activePartChanged 0x83b8930 khtml (part): new active frame 0x83b8930 kio (Scheduler): reparseConfiguration( ) Program received signal SIGPIPE, Broken pipe. [Switching to Thread 1024 (LWP 16377)] 0x420dae54 in write () from /lib/i686/libc.so.6 (gdb) bt #0 0x420dae54 in write () from /lib/i686/libc.so.6 #1 0x411f2b18 in __DTOR_END__ () from /lib/i686/libpthread.so.0 #2 0x42076925 in _IO_new_file_write () from /lib/i686/libc.so.6 #3 0x420769b9 in new_do_write () from /lib/i686/libc.so.6 #4 0x4207657f in _IO_new_do_write () from /lib/i686/libc.so.6 #5 0x42075c78 in _IO_new_file_sync () from /lib/i686/libc.so.6 #6 0x4206b8fe in fflush () from /lib/i686/libc.so.6 #7 0x402f3dfa in KIO::Connection::sendnow (this=0x81d92f4, _cmd=79, data=@0xbfffe740) at connection.cpp:192 #8 0x402f3899 in KIO::Connection::send (this=0x81d92f4, cmd=79, data=@0xbfffe740) at connection.cpp:99 #9 0x402e89b5 in KIO::Slave::send (this=0x81d9290, cmd=79, arr=@0xbfffe740) at slave.cpp:288 #10 0x402efa83 in KIO::Scheduler::process (this=0x81dd998, fun=@0xbfffe960, data=@0xbfffe970, replyType=@0xbfffe920, replyData=@0xbfffe910) at scheduler.cpp:186 #11 0x4098767f in DCOPClient::receive (this=0x8096868, objId=@0xbfffe950, fun=@0xbfffe960, data=@0xbfffe970, replyType=@0xbfffe920, replyData=@0xbfffe910) at dcopclient.cpp:1601 #12 0x40981910 in DCOPProcessInternal (d=0x8098c50, opcode=1, key=1, dataReceived=@0xbfffea60, canPost=true) at dcopclient.cpp:507 #13 0x40981267 in DCOPProcessMessage (iceConn=0x8099648, clientObject=0x8098c50, opcode=1, length=91, replyWait=0x0, replyWaitRet=0xbfffeadc) at dcopclient.cpp:418 #14 0x40996d71 in KDE_IceProcessMessages (iceConn=0x8099648, replyWait=0x0, replyReadyRet=0x0) at process.c:325 #15 0x40988a1d in DCOPClient::processSocketData (this=0x8096868, fd=11) at dcopclient.cpp:1944 #16 0x4098a145 in DCOPClient::qt_invoke (this=0x8096868, _id=2, _o=0xbfffec30) at dcopclient.moc:174 #17 0x40c4db92 in QObject::activate_signal () from /opt/qt33f/lib/libqt-mt.so.3 #18 0x40c4ddf9 in QObject::activate_signal () from /opt/qt33f/lib/libqt-mt.so.3 #19 0x40f1a93d in QSocketNotifier::activated () from /opt/qt33f/lib/libqt-mt.so.3 #20 0x40c65bf7 in QSocketNotifier::event () from /opt/qt33f/lib/libqt-mt.so.3 #21 0x40bfe618 in QApplication::internalNotify () from /opt/qt33f/lib/libqt-mt.so.3 #22 0x40bfe264 in QApplication::notify () from /opt/qt33f/lib/libqt-mt.so.3 #23 0x4081ddea in KApplication::notify (this=0xbffff470, receiver=0x809a118, event=0xbfffef20) at kapplication.cpp:506 #24 0x40bf0726 in QEventLoop::activateSocketNotifiers () from /opt/qt33f/lib/libqt-mt.so.3 #25 0x40bb4558 in QEventLoop::processEvents () from /opt/qt33f/lib/libqt-mt.so.3 #26 0x40c0d18c in QEventLoop::enterLoop () from /opt/qt33f/lib/libqt-mt.so.3 #27 0x40c0d0d5 in QEventLoop::exec () from /opt/qt33f/lib/libqt-mt.so.3 #28 0x40bfe7a0 in QApplication::exec () from /opt/qt33f/lib/libqt-mt.so.3 #29 0x40066a32 in kdemain (argc=1, argv=0xbffff5d4) at konq_main.cc:184 #30 0x42017589 in __libc_start_main () from /lib/i686/libc.so.6
Tommi: but it isn't the konqueror process that is eating CPU is it? It is the kio_http process, right?
I can not reproduce this anymore and I don't remember the hanging process name. I have not seen this hang for a long time.
Assumed to be fixed