Summary: | Kget crashes when pausing some running downloads | ||
---|---|---|---|
Product: | [Applications] kget | Reporter: | Woodhouse <m.r.holthuis> |
Component: | general | Assignee: | KGet authors <kget> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | itayff |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Woodhouse
2005-04-21 20:47:54 UTC
Only one bug per report please. Backtrace at hand? I am also getting crashes all the time when pausing/stopping downloads - didn't find a pattern but the crash happens in about 1 of 4 paused downloads. I get sygnal 11 - here's what's on the terminal: kio (KIOJob): SlaveInterface::sendResumeAnswer ok for resuming :true kget: [void Transfer::slotRequestDelay()] |--( GUI )--| >>>>Entering kget: [void Transfer::logMessage(const QString&)] |--( GUI )--| >>>>Entering Delaying kget: [void Transfer::logMessage(const QString&)] |--( GUI )--| >>>>Leaving kget: [void Slave::Op(Slave::SlaveCommand)] |--TH_ID ( 3061668256 )--| >>>>Entering _cmd = 5 kget: [void Slave::Op(Slave::SlaveCommand)] |--TH_ID ( 3061668256 )--| >>>>Leaving kget: [void Transfer::slotRequestDelay()] |--( GUI )--| >>>>Leaving kget: [virtual void Slave::run()] |--TH_ID ( 3058371488 )--| FETCHED COMMAND DELAY kio (KIOJob): Job::kill this=0x81aaa58 KIO::FileCopyJob m_progressId=0 quietly=true kio (Scheduler): Scheduler: killing slave 12492 kio (Slave): killing slave pid=12492 (file://) KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kget path = <unknown> pid = 12469 kio (KIOJob): Job::kill this=0x823bfc8 KIO::TransferJob m_progressId=0 quietly=true kio (Scheduler): Scheduler: killing slave 12493 kio (Slave): killing slave pid=12493 (<server name removed>) kio (KIOJob): Job::kill this=0x81acfc8 KIO::TransferJob m_progressId=0 quietly=true In this case I simply resumed one of 4 downloads, then paused it. After a couple of time it crashed. p.s. my system is Mandriva Cooker, KDE 3.5.3, kget 0.8.5, currently running under Gnome 2.15. I also suffered a similar problem, but I'm not sure the backtrace is the same. Find it below: (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1500686048 (LWP 14435)] [New Thread -1507058768 (LWP 14440)] [KCrash handler] #6 0xa7cf662b in KIO::Slave::resume (this=0x819ec40) at /home/ana/Debian/kdelibs/kdelibs-3.5.5a.dfsg.1/./kio/kio/slave.cpp:266 #7 0xa7cf689b in KIO::TransferJob::resume (this=0x819b630) at /home/ana/Debian/kdelibs/kdelibs-3.5.5a.dfsg.1/./kio/kio/job.cpp:1099 #8 0xa7d55740 in KIO::FileCopyJob::slotData (this=0xa59012e0, data=@0xafa563f0) at /home/ana/Debian/kdelibs/kdelibs-3.5.5a.dfsg.1/./kio/kio/job.cpp:1812 #9 0xa7d6b363 in KIO::FileCopyJob::qt_invoke (this=0xa59012e0, _id=7, _o=0xafa560f0) at ./jobclasses.moc:1556 #10 0xa6f70cb3 in QObject::activate_signal (this=0x81a07d8, clist=0x819e9e8, o=0xafa560f0) at kernel/qobject.cpp:2356 #11 0xa7d0473d in KIO::TransferJob::data (this=0x81a07d8, t0=0x81a07d8, t1=@0xafa563f0) at ./jobclasses.moc:993 #12 0xa7d047c8 in KIO::TransferJob::slotData (this=0x81a07d8, _data=@0xafa563f0) at /home/ana/Debian/kdelibs/kdelibs-3.5.5a.dfsg.1/./kio/kio/job.cpp:906 #13 0xa7d41e19 in KIO::TransferJob::qt_invoke (this=0x81a07d8, _id=18, _o=0xafa561e4) at ./jobclasses.moc:1072 #14 0xa6f70cb3 in QObject::activate_signal (this=0x81a0c30, clist=0x81a2308, o=0xafa561e4) at kernel/qobject.cpp:2356 #15 0xa7d00e7e in KIO::SlaveInterface::data (this=0x81a0c30, t0=@0xafa563f0) at ./slaveinterface.moc:194 #16 0xa7d61b42 in KIO::SlaveInterface::dispatch (this=0x81a0c30, _cmd=100, rawdata=@0xafa563f0) at /home/ana/Debian/kdelibs/kdelibs-3.5.5a.dfsg.1/./kio/kio/slaveinterface.cpp:234 #17 0xa7d5fed8 in KIO::SlaveInterface::dispatch (this=0x81a0c30) at /home/ana/Debian/kdelibs/kdelibs-3.5.5a.dfsg.1/./kio/kio/slaveinterface.cpp:173 #18 0xa7d10fab in KIO::Slave::gotInput (this=0x81a0c30) at /home/ana/Debian/kdelibs/kdelibs-3.5.5a.dfsg.1/./kio/kio/slave.cpp:300 #19 0xa7d4fa60 in KIO::Slave::qt_invoke (this=0x81a0c30, _id=4, _o=0xafa56518) at ./slave.moc:113 #20 0xa6f70cb3 in QObject::activate_signal (this=0x819e0a0, clist=0x819e8f0, o=0xafa56518) at kernel/qobject.cpp:2356 #21 0xa6f715ba in QObject::activate_signal (this=0x819e0a0, signal=2, param=14) at kernel/qobject.cpp:2449 #22 0xa72faa87 in QSocketNotifier::activated (this=0x819e0a0, t0=14) at .moc/debug-shared-mt/moc_qsocketnotifier.cpp:85 #23 0xa6f9345e in QSocketNotifier::event (this=0x819e0a0, e=0xafa56870) at kernel/qsocketnotifier.cpp:258 #24 0xa6f08bd6 in QApplication::internalNotify (this=0xafa56af0, receiver=0x819e0a0, e=0xafa56870) at kernel/qapplication.cpp:2635 #25 0xa6f0a9f3 in QApplication::notify (this=0xafa56af0, receiver=0x819e0a0, e=0xafa56870) at kernel/qapplication.cpp:2358 #26 0xa7885e0e in KApplication::notify (this=0xafa56af0, receiver=0x819e0a0, event=0xafa56870) at /home/ana/Debian/kdelibs/kdelibs-3.5.5a.dfsg.1/./kdecore/kapplication.cpp:550 #27 0xa6e9c3d1 in QApplication::sendEvent (receiver=0x819e0a0, event=0xafa56870) at ../include/qapplication.h:520 #28 0xa6efaf89 in QEventLoop::activateSocketNotifiers (this=0x80b5b68) at kernel/qeventloop_unix.cpp:578 #29 0xa6eb0704 in QEventLoop::processEvents (this=0x80b5b68, flags=4) at kernel/qeventloop_x11.cpp:383 #30 0xa6f23129 in QEventLoop::enterLoop (this=0x80b5b68) at kernel/qeventloop.cpp:198 #31 0xa6f22f4a in QEventLoop::exec (this=0x80b5b68) at kernel/qeventloop.cpp:145 #32 0xa6f0a76f in QApplication::exec (this=0xafa56af0) at kernel/qapplication.cpp:2758 #33 0x08062908 in ?? () #34 0xafa56af0 in ?? () #35 0x00000001 in ?? () #36 0x00000001 in ?? () #37 0x00000000 in ?? () Please, feel free to created another bug or reply me to do so in case you find it convenient. *** Bug 139584 has been marked as a duplicate of this bug. *** This is just to say that this also happens when entering into offline mode. This is also reported in Debian BTS at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=410743 Due to the move from the make_kget_cool branch back into kdenetwork, this issue has been resolved. For more details about the new KGet please have a look at this page (1st article): http://commit-digest.org/issues/2007-02-25/ |