Bug 139016 - konqueror takes 99% cpu after kget couldn't connect to one download source.
Summary: konqueror takes 99% cpu after kget couldn't connect to one download source.
Status: RESOLVED DUPLICATE of bug 51965
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-12-19 17:55 UTC by Raúl
Modified: 2006-12-20 08:09 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Raúl 2006-12-19 17:55:39 UTC
Version:           3.5.5 (using KDE 3.5.5, Debian Package 4:3.5.5a.dfsg.1-5 (4.0))
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.18p4s

I was downloading a very big(5GB) file with kget. The server was unavailable at a certain moment, after a while, when I noticed, both kget and konqueror were taking 99% cpu.

I have several backtraces of kget with some working interval between them, since kget still worked:

#0  0xa731182c in QGDict::look_ascii (this=0x80b77d0, key=0xa73f6d9c "destroyed()", d=0x0, op=0) at tools/qgdict.cpp:368
#1  0xa700dfb4 in QAsciiDict<QMetaData const>::find (this=0x80b77d0, k=0xa73f6d9c "destroyed()") at ../include/qasciidict.h:71
#2  0xa700b84d in QMetaObject::findSignal (this=0x811ba70, n=0xa73f6d9c "destroyed()", super=true) at kernel/qmetaobject.cpp:419
#3  0xa701cab2 in QObject::connect (sender=0x81616e0, signal=0xa73f6d9c "destroyed()", receiver=0x81abb38, member=0xa73f6d88 "1objectDestroyed()")
    at kernel/qobject.cpp:1741
#4  0xa6fe1b0f in QGuardedPtrPrivate (this=0x81abb38, o=0x81616e0) at kernel/qguardedptr.cpp:199
#5  0xa703ad1c in QGuardedPtr (this=0xafb17da0, o=0x81616e0) at ../include/qguardedptr.h:74
#6  0xa703a7d4 in QSignal::activate (this=0x81616e0) at kernel/qsignal.cpp:208
#7  0xa7042208 in QSingleShotTimer::event (this=0x81616b8) at kernel/qtimer.cpp:286
#8  0xa6fb2bd6 in QApplication::internalNotify (this=0xafb18350, receiver=0x81616b8, e=0xafb180b8) at kernel/qapplication.cpp:2635
#9  0xa6fb49f3 in QApplication::notify (this=0xafb18350, receiver=0x81616b8, e=0xafb180b8) at kernel/qapplication.cpp:2358
#10 0xa792fe0e in KApplication::notify (this=0xafb18350, receiver=0x81616b8, event=0xafb180b8)
    at /home/ana/Debian/kdelibs/kdelibs-3.5.5a.dfsg.1/./kdecore/kapplication.cpp:550
#11 0xa6f463d1 in QApplication::sendEvent (receiver=0x81616b8, event=0xafb180b8) at ../include/qapplication.h:520
#12 0xa6fa55d3 in QEventLoop::activateTimers (this=0x80b5b68) at kernel/qeventloop_unix.cpp:556
#13 0xa6f5a71f in QEventLoop::processEvents (this=0x80b5b68, flags=4) at kernel/qeventloop_x11.cpp:389
#14 0xa6fcd129 in QEventLoop::enterLoop (this=0x80b5b68) at kernel/qeventloop.cpp:198
#15 0xa6fccf4a in QEventLoop::exec (this=0x80b5b68) at kernel/qeventloop.cpp:145
#16 0xa6fb476f in QApplication::exec (this=0xafb18350) at kernel/qapplication.cpp:2758
#17 0x08062908 in ?? ()
#18 0xafb18350 in ?? ()
#19 0x00000001 in ?? ()
#20 0x00000001 in ?? ()
#21 0x00000000 in ?? ()
Continuing.

Program received signal SIGINT, Interrupt.
[Switching to Thread -1499989728 (LWP 8671)]
0xa7313b00 in QGListIterator::operator++ (this=0xafb17df4) at tools/qglist.cpp:1226
1226	tools/qglist.cpp: No existe el fichero o el directorio.
	in tools/qglist.cpp
Undefined command: "bg".  Try "help".
#0  0xa7313b00 in QGListIterator::operator++ (this=0xafb17df4) at tools/qglist.cpp:1226
#1  0xa6f84dab in QPtrListIterator<QObject>::operator++ (this=0xafb17df4) at ../include/qptrlist.h:176
#2  0xa6fb29a8 in QApplication::internalNotify (this=0xafb18350, receiver=0x81616b8, e=0xafb180b8) at kernel/qapplication.cpp:2567
#3  0xa6fb49f3 in QApplication::notify (this=0xafb18350, receiver=0x81616b8, e=0xafb180b8) at kernel/qapplication.cpp:2358
#4  0xa792fe0e in KApplication::notify (this=0xafb18350, receiver=0x81616b8, event=0xafb180b8)
    at /home/ana/Debian/kdelibs/kdelibs-3.5.5a.dfsg.1/./kdecore/kapplication.cpp:550
#5  0xa6f463d1 in QApplication::sendEvent (receiver=0x81616b8, event=0xafb180b8) at ../include/qapplication.h:520
#6  0xa6fa55d3 in QEventLoop::activateTimers (this=0x80b5b68) at kernel/qeventloop_unix.cpp:556
#7  0xa6f5a71f in QEventLoop::processEvents (this=0x80b5b68, flags=4) at kernel/qeventloop_x11.cpp:389
#8  0xa6fcd129 in QEventLoop::enterLoop (this=0x80b5b68) at kernel/qeventloop.cpp:198
#9  0xa6fccf4a in QEventLoop::exec (this=0x80b5b68) at kernel/qeventloop.cpp:145
#10 0xa6fb476f in QApplication::exec (this=0xafb18350) at kernel/qapplication.cpp:2758
#11 0x08062908 in ?? ()
#12 0xafb18350 in ?? ()
#13 0x00000001 in ?? ()
#14 0x00000001 in ?? ()
#15 0x00000000 in ?? ()
Continuing.

Program received signal SIGINT, Interrupt.
0xa7fe7410 in __kernel_vsyscall ()
#0  0xa7fe7410 in __kernel_vsyscall ()
#1  0xa75f6fc1 in select () from /lib/tls/i686/cmov/libc.so.6
#2  0xa6f5a258 in QEventLoop::processEvents (this=0x80b5b68, flags=4) at kernel/qeventloop_x11.cpp:291
#3  0xa6fcd129 in QEventLoop::enterLoop (this=0x80b5b68) at kernel/qeventloop.cpp:198
#4  0xa6fccf4a in QEventLoop::exec (this=0x80b5b68) at kernel/qeventloop.cpp:145
#5  0xa6fb476f in QApplication::exec (this=0xafb18350) at kernel/qapplication.cpp:2758
#6  0x08062908 in ?? ()
#7  0xafb18350 in ?? ()
#8  0x00000001 in ?? ()
#9  0x00000001 in ?? ()
#10 0x00000000 in ?? ()
Continuing.

Program received signal SIGINT, Interrupt.
0xa6f1eda0 in ?? () from /usr/lib/libqt-mt.so.3
#0  0xa6f1eda0 in ?? () from /usr/lib/libqt-mt.so.3
#1  0xa73a3ef1 in QSignal::metaObject (this=0x81616e0) at .moc/debug-shared-mt/../../kernel/qsignal.h:49
#2  0xa701ca54 in QObject::connect (sender=0x81616e0, signal=0xa73f6d9b "2destroyed()", receiver=0x81900c8, member=0xa73f6d88 "1objectDestroyed()")
    at kernel/qobject.cpp:1732
#3  0xa6fe1b0f in QGuardedPtrPrivate (this=0x81900c8, o=0x81616e0) at kernel/qguardedptr.cpp:199
#4  0xa703ad1c in QGuardedPtr (this=0xafb17da0, o=0x81616e0) at ../include/qguardedptr.h:74
#5  0xa703a7d4 in QSignal::activate (this=0x81616e0) at kernel/qsignal.cpp:208
#6  0xa7042208 in QSingleShotTimer::event (this=0x81616b8) at kernel/qtimer.cpp:286
#7  0xa6fb2bd6 in QApplication::internalNotify (this=0xafb18350, receiver=0x81616b8, e=0xafb180b8) at kernel/qapplication.cpp:2635
#8  0xa6fb49f3 in QApplication::notify (this=0xafb18350, receiver=0x81616b8, e=0xafb180b8) at kernel/qapplication.cpp:2358
#9  0xa792fe0e in KApplication::notify (this=0xafb18350, receiver=0x81616b8, event=0xafb180b8)
    at /home/ana/Debian/kdelibs/kdelibs-3.5.5a.dfsg.1/./kdecore/kapplication.cpp:550
#10 0xa6f463d1 in QApplication::sendEvent (receiver=0x81616b8, event=0xafb180b8) at ../include/qapplication.h:520
#11 0xa6fa55d3 in QEventLoop::activateTimers (this=0x80b5b68) at kernel/qeventloop_unix.cpp:556
#12 0xa6f5a71f in QEventLoop::processEvents (this=0x80b5b68, flags=4) at kernel/qeventloop_x11.cpp:389
#13 0xa6fcd129 in QEventLoop::enterLoop (this=0x80b5b68) at kernel/qeventloop.cpp:198
#14 0xa6fccf4a in QEventLoop::exec (this=0x80b5b68) at kernel/qeventloop.cpp:145
#15 0xa6fb476f in QApplication::exec (this=0xafb18350) at kernel/qapplication.cpp:2758
#16 0x08062908 in ?? ()
#17 0xafb18350 in ?? ()
#18 0x00000001 in ?? ()
#19 0x00000001 in ?? ()
#20 0x00000000 in ?? ()

After this I killed kget, then konqueror on it's own take the 99% cpu with this backtrace:
#0  QGList::first (this=0x80d86e0) at tools/qglist.cpp:837
#1  0xa72244e1 in QPtrList<TimerInfo>::first (this=0x80d86e0) at ../include/qptrlist.h:109
#2  0xa72234ad in QEventLoop::activateTimers (this=0x80cc048) at kernel/qeventloop_unix.cpp:537
#3  0xa71d871f in QEventLoop::processEvents (this=0x80cc048, flags=4) at kernel/qeventloop_x11.cpp:389
#4  0xa724b129 in QEventLoop::enterLoop (this=0x80cc048) at kernel/qeventloop.cpp:198
#5  0xa724af4a in QEventLoop::exec (this=0x80cc048) at kernel/qeventloop.cpp:145
#6  0xa723276f in QApplication::exec (this=0xaff0c69c) at kernel/qapplication.cpp:2758
#7  0xa667a495 in kdemain (argc=2, argv=0x8084338) at /home/sid-user/kdebase/kdebase-3.5.5/./konqueror/konq_main.cc:206
#8  0xa7f8d524 in kdeinitmain (argc=2, argv=0x8084338) at konqueror_dummy.cc:3
#9  0x0804e457 in launch (argc=2, _name=0x80846b4 "konqueror", args=0x80846c6 "", cwd=0x0, envc=1, envs=0x80846d7 "", reset_env=false, tty=0x0, 
    avoid_loops=false, startup_id_str=0x80846dc "Debian2;1166116945;209220;5359_TIME2180807905")
    at /home/ana/Debian/kdelibs/kdelibs-3.5.5a.dfsg.1/./kinit/kinit.cpp:673
#10 0x0804ecf9 in handle_launcher_request (sock=9) at /home/ana/Debian/kdelibs/kdelibs-3.5.5a.dfsg.1/./kinit/kinit.cpp:1240
#11 0x0804f092 in handle_requests (waitForPid=0) at /home/ana/Debian/kdelibs/kdelibs-3.5.5a.dfsg.1/./kinit/kinit.cpp:1443
#12 0x080502b1 in main (argc=5, argv=0xaff0d154, envp=0xaff0d16c) at /home/ana/Debian/kdelibs/kdelibs-3.5.5a.dfsg.1/./kinit/kinit.cpp:1909
#13 0xa7cfaea8 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#14 0x0804b911 in _start () at ../sysdeps/i386/elf/start.S:119
The program is running.  Quit anyway (and detach it)? (y or n) Detaching from program: /usr/bin/kdeinit, process 20798

Sorry for this long backtrace, but I think you prefer like this than attached.

Tell me if there's anything I can do.
Comment 1 Tommi Tervo 2006-12-20 08:09:50 UTC

*** This bug has been marked as a duplicate of 51965 ***