Bug 306501 - kget stalls, then crashes after suspend resume
Summary: kget stalls, then crashes after suspend resume
Status: RESOLVED WORKSFORME
Alias: None
Product: kget
Classification: Applications
Component: general (show other bugs)
Version: 2.9.1
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: KGet authors
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2012-09-09 16:27 UTC by squan
Modified: 2018-10-27 04:03 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description squan 2012-09-09 16:27:42 UTC
Application: kget (2.9.1)
KDE Platform Version: 4.9.1 "release 561"
Qt Version: 4.8.2
Operating System: Linux 3.4.6-2.10-desktop x86_64
Distribution: "openSUSE 12.2 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
1) start a http download
2) schedule a suspend after expected end of download
   (with e.g. #sleep 1h; powersave -u')
3) download will stall randomly for no apparent reason
  (often kget pause and resume do not fix this and the only thing
  to resume the download is to just restart kget)
4) computer suspends at scheduled time
5) resume computer
=> kget crashes

The crash can be reproduced some of the time.

-- Backtrace:
Application: KGet (kget), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#6  KIO::FileJob::seek (this=0x0, offset=1064960000) at /usr/src/debug/kdelibs-4.9.1/build/kio/filejob.moc:184
#7  0x00007ff59dd289ff in QMetaObject::activate (sender=0x15b41f0, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fffcc6f0e20) at kernel/qobject.cpp:3556
#8  0x00007ff59f95394c in TransferDataSource::data (this=<optimized out>, _t1=1064960000, _t2=..., _t3=<optimized out>) at /usr/src/debug/kdenetwork-4.9.1/build/kget/transferdatasource.moc:167
#9  0x00007ff59f953c77 in TransferDataSource::qt_static_metacall (_o=0x0, _c=1064960000, _id=22971393, _a=0x7fffcc6f0fef) at /usr/src/debug/kdenetwork-4.9.1/build/kget/transferdatasource.moc:87
#10 0x00007ff59dd289ff in QMetaObject::activate (sender=0x15e8430, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fffcc6f0fb0) at kernel/qobject.cpp:3556
#11 0x00007ff5863ae089 in Segment::data (this=this@entry=0x15e8430, _t1=1064960000, _t2=..., _t3=@0x7fffcc6f0fef: true, _t3@entry=@0x7fffcc6f0fef: false) at /usr/src/debug/kdenetwork-4.9.1/build/kget/transfer-plugins/multisegmentkio/segment.moc:148
#12 0x00007ff5863ae19d in Segment::writeBuffer (this=this@entry=0x15e8430) at /usr/src/debug/kdenetwork-4.9.1/kget/transfer-plugins/multisegmentkio/segment.cpp:237
#13 0x00007ff5863aefb0 in Segment::slotData (this=0x15e8430, _data=...) at /usr/src/debug/kdenetwork-4.9.1/kget/transfer-plugins/multisegmentkio/segment.cpp:225
#14 0x00007ff59dd289ff in QMetaObject::activate (sender=0x13ea0c0, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fffcc6f1220) at kernel/qobject.cpp:3556
#15 0x00007ff59feeb234 in KIO::TransferJob::data (this=this@entry=0x13ea0c0, _t1=_t1@entry=0x13ea0c0, _t2=...) at /usr/src/debug/kdelibs-4.9.1/build/kio/jobclasses.moc:447
#16 0x00007ff59feeb293 in KIO::TransferJob::slotData (this=0x13ea0c0, _data=...) at /usr/src/debug/kdelibs-4.9.1/kio/kio/job.cpp:981
#17 0x00007ff59dd289ff in QMetaObject::activate (sender=0x15bfcf0, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fffcc6f13d0) at kernel/qobject.cpp:3556
#18 0x00007ff59ff886c2 in KIO::SlaveInterface::data (this=this@entry=0x15bfcf0, _t1=...) at /usr/src/debug/kdelibs-4.9.1/build/kio/slaveinterface.moc:160
#19 0x00007ff59ff8b1d0 in KIO::SlaveInterface::dispatch (this=0x15bfcf0, _cmd=100, rawdata=...) at /usr/src/debug/kdelibs-4.9.1/kio/kio/slaveinterface.cpp:160
#20 0x00007ff59ff8801a in KIO::SlaveInterface::dispatch (this=0x15bfcf0) at /usr/src/debug/kdelibs-4.9.1/kio/kio/slaveinterface.cpp:88
#21 0x00007ff59ff7c47e in KIO::Slave::gotInput (this=0x15bfcf0) at /usr/src/debug/kdelibs-4.9.1/kio/kio/slave.cpp:344
#22 0x00007ff59dd289ff in QMetaObject::activate (sender=0x15b1d20, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3556
#23 0x00007ff59febeba2 in dequeue (this=<optimized out>) at /usr/src/debug/kdelibs-4.9.1/kio/kio/connection.cpp:82
#24 KIO::ConnectionPrivate::dequeue (this=0x15cec20) at /usr/src/debug/kdelibs-4.9.1/kio/kio/connection.cpp:71
#25 0x00007ff59dd26b4e in QObject::event (this=0x15b1d20, e=<optimized out>) at kernel/qobject.cpp:1204
#26 0x00007ff59d0bd64c in QApplicationPrivate::notify_helper (this=this@entry=0x10bd610, receiver=receiver@entry=0x15b1d20, e=e@entry=0x10a5bb0) at kernel/qapplication.cpp:4551
#27 0x00007ff59d0c1aca in QApplication::notify (this=0x7fffcc6f2580, receiver=0x15b1d20, e=0x10a5bb0) at kernel/qapplication.cpp:4412
#28 0x00007ff5a04d60d6 in KApplication::notify (this=0x7fffcc6f2580, receiver=0x15b1d20, event=0x10a5bb0) at /usr/src/debug/kdelibs-4.9.1/kdeui/kernel/kapplication.cpp:311
#29 0x00007ff59dd1216e in QCoreApplication::notifyInternal (this=0x7fffcc6f2580, receiver=receiver@entry=0x15b1d20, event=event@entry=0x10a5bb0) at kernel/qcoreapplication.cpp:915
#30 0x00007ff59dd15ad1 in sendEvent (event=0x10a5bb0, receiver=0x15b1d20) at kernel/qcoreapplication.h:231
#31 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x103c170) at kernel/qcoreapplication.cpp:1539
#32 0x00007ff59dd40243 in sendPostedEvents () at kernel/qcoreapplication.h:236
#33 postEventSourceDispatch (s=0x109a9b0) at kernel/qeventdispatcher_glib.cpp:279
#34 0x00007ff597c86405 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#35 0x00007ff597c86738 in ?? () from /usr/lib64/libglib-2.0.so.0
#36 0x00007ff597c867f4 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#37 0x00007ff59dd403d6 in QEventDispatcherGlib::processEvents (this=0x10419f0, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#38 0x00007ff59d15d7ae in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#39 0x00007ff59dd10ebf in QEventLoop::processEvents (this=this@entry=0x7fffcc6f20e0, flags=...) at kernel/qeventloop.cpp:149
#40 0x00007ff59dd11148 in QEventLoop::exec (this=0x7fffcc6f20e0, flags=...) at kernel/qeventloop.cpp:204
#41 0x00007ff59dd15de8 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1187
#42 0x000000000042b367 in main (argc=1, argv=0x7fffcc6f26c8) at /usr/src/debug/kdenetwork-4.9.1/kget/main.cpp:149

Reported using DrKonqi
Comment 1 David E. Narvaez 2013-02-21 05:01:45 UTC
Can you elaborate on step 3 of the information above? My random guess is that this can be reproduced only when 3 happens and it may not always happen, am I right?
Comment 2 Christoph Feck 2013-03-06 20:36:43 UTC
If you can provide the information requested in comment #1, please add it.
Comment 3 Christoph Feck 2013-04-14 14:10:41 UTC
To further investigate this issue, KDE developers need the information requested in comment #1. If you can provide it, or need help with finding that information, please add a comment.
Comment 4 Andrew Crouthamel 2018-09-24 02:07:05 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Andrew Crouthamel 2018-10-27 04:03:13 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!