Bug 260843 - kget crashes when resuming bittorrent downloads after running out of diskspace
Summary: kget crashes when resuming bittorrent downloads after running out of diskspace
Status: RESOLVED WORKSFORME
Alias: None
Product: kget
Classification: Applications
Component: torrent (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: KGet authors
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2010-12-21 00:27 UTC by Bernhard Rosenkraenzer
Modified: 2018-10-27 04:13 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 Bernhard Rosenkraenzer 2010-12-21 00:27:16 UTC
Version:           unspecified (using KDE 4.5.85) 
OS:                Linux

I was downloading some files with kget using bittorrent when I ran out of diskspace.
kget crashed; now (after freeing up space) trying to start kget results in a crash.

Application: KGet (kget), signal: Segmentation fault
[Current thread is 1 (process 6348)]

Thread 1 (process 6348):
#0  0xffffe424 in __kernel_vsyscall ()
#1  0xb6c6fddb in pthread_cond_wait () from /lib/libpthread.so.0
#2  0xb651e327 in ?? () from /usr/lib/libQtCore.so.4
#3  0xb651aaec in QMutex::lock() () from /usr/lib/libQtCore.so.4
#4  0xae8c0ab1 in bt::Log::lock() () from /usr/lib/libktorrent.so.2
#5  0xae8c0cfc in bt::Out(unsigned int) () from /usr/lib/libktorrent.so.2
#6  0xae9072b4 in bt::Server::changePort(unsigned short) () from /usr/lib/libktorrent.so.2
#7  0xae9069ae in bt::Globals::initTCPServer(unsigned short) () from /usr/lib/libktorrent.so.2
#8  0xaea14117 in BTTransfer::btTransferInit (this=0xa03bfd8, src=..., data=...) at /usr/src/debug/kdenetwork/kget/transfer-plugins/bittorrent/bttransfer.cpp:425
#9  0xaea15504 in BTTransfer::start (this=0xa03bfd8) at /usr/src/debug/kdenetwork/kget/transfer-plugins/bittorrent/bttransfer.cpp:139
#10 0xb70382d9 in Scheduler::updateQueue (this=0x9e7e7d8, queue=0x9f8ace8) at /usr/src/debug/kdenetwork/kget/core/scheduler.cpp:285
#11 0xb70226c0 in JobQueue::append (this=0x9f8ace8, jobs=...) at /usr/src/debug/kdenetwork/kget/core/jobqueue.cpp:95
#12 0xb7047b3b in TransferGroup::append (this=0x9f8ace8, transfers=...) at /usr/src/debug/kdenetwork/kget/core/transfergroup.cpp:102
#13 0xb703c2e1 in TransferTreeModel::addTransfers (this=0x9f53248, transfers=..., group=0x80) at /usr/src/debug/kdenetwork/kget/core/transfertreemodel.cpp:241
#14 0xb7030a08 in KGet::createTransfers (dataItems=...) at /usr/src/debug/kdenetwork/kget/core/kget.cpp:915
#15 0xb7033f73 in KGet::addTransfers (elements=..., groupName=...) at /usr/src/debug/kdenetwork/kget/core/kget.cpp:277
#16 0xb7046717 in TransferGroup::load (this=0x9f8ace8, e=...) at /usr/src/debug/kdenetwork/kget/core/transfergroup.cpp:399
#17 0xb7026acf in KGet::load (filename=...) at /usr/src/debug/kdenetwork/kget/core/kget.cpp:559
#18 0x080e7e64 in MainWindow::init (this=0x9ebc858) at /usr/src/debug/kdenetwork/kget/mainwindow.cpp:356
#19 0x080f379a in KGetApp::newInstance (this=0xbfcf9f58) at /usr/src/debug/kdenetwork/kget/main.cpp:71
#20 0xb751e658 in ?? () from /usr/lib/libkdeui.so.5
Backtrace stopped: previous frame inner to this frame (corrupt stack?)


Reproducible: Always
Comment 1 Lukas Appelhans 2011-01-07 01:16:05 UTC
Joris, this might be of interest for libktorrent...

Lukas
Comment 2 Joris Guisson 2011-01-07 19:01:38 UTC
Is this a complete backtrace ?

Would it be possible to run kget under valgrind ? That should reveal where things start to go wrong.
Comment 3 Lukas Appelhans 2011-02-06 12:15:17 UTC
Let's mark it as needs information...

Lukas
Comment 4 Andrew Crouthamel 2018-09-22 02:04:20 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:13:25 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!