I had this problem twice this night.

KTorrent running in systray, and after some hours it uses 80% cpu while it can't be launched in screen anymore. I had to kill the pid to get going again.
For some reason the ktorrent --debug doesn't work here anymore either, so i can't supply any more than this i am afraid.

I saw this too. I left KT running this night and in the morning I found it not responding with 99% CPU usage.

@George: Maybe that infinite loop you experienced yesterday?

I've not experienced this bug anymore since i disabled DHT this morning.

I think it's DHT related too.
Actually, I've just experienced it again but this time I saw KT log which had this message repeated many times:

DHT: refreshing bucket

It seems that there's an infinite loop which causes KT to stop responding and writes this message over and over again.

Something wrong with the bucket refresh, shouldn't be much trouble to fix it.

This should not happen anymore. Forgot to update a timestamp when the bucket was going to be refreshed, which caused the bucket to be continously refreshed.

I was planning to release the beta this evening, but seeing this bug it may be better to let KT run overnight to see if something like this still happens. I have allready made the tar.gz (with my fix included)

If anybody wants to test it :
http://ktorrent.org/downloads/2.0beta1/ ... ta1.tar.gz

If no more problems like this come up, we will release tomorrow.

I assume this will fix my dht freezing problems? I managed to attach gdb and grab a backtrace:

Code: Select all

#0  0xa7eb1d9f in std::_Rb_tree<unsigned char, std::pair<unsigned char const, dht::RPCCall*>, std::_Select1st<std::pair<unsigned char const, dht::RPCCall*> >, std::less<unsigned char>, std::allocator<std::pair<unsigned char const, dht::RPCCall*> > >::find () from /usr/kde/3.5/lib/libktorrent.so.0
#1  0xa7eb0ae0 in dht::RPCServer::doCall () from /usr/kde/3.5/lib/libktorrent.so.0
#2  0xa7ead3e5 in dht::KBucket::pingQuestionable () from /usr/kde/3.5/lib/libktorrent.so.0
#3  0xa7eadbd8 in dht::KBucket::onResponse () from /usr/kde/3.5/lib/libktorrent.so.0
#4  0xa7eafbec in dht::RPCCallListener::qt_invoke () from /usr/kde/3.5/lib/libktorrent.so.0
#5  0xa7029de9 in QObject::activate_signal () from /usr/qt/3/lib/libqt-mt.so.3
#6  0xa7eafcce in dht::RPCCall::onCallResponse () from /usr/kde/3.5/lib/libktorrent.so.0
#7  0xa7eafd68 in dht::RPCCall::response () from /usr/kde/3.5/lib/libktorrent.so.0
#8  0xa7eb1069 in dht::RPCServer::readPacket () from /usr/kde/3.5/lib/libktorrent.so.0
#9  0xa7eb12a2 in dht::RPCServer::qt_invoke () from /usr/kde/3.5/lib/libktorrent.so.0
#10 0xa7029de9 in QObject::activate_signal () from /usr/qt/3/lib/libqt-mt.so.3
#11 0xa702a5bd in QObject::activate_signal () from /usr/qt/3/lib/libqt-mt.so.3
#12 0xa772869a in KNetwork::KClientSocketBase::readyRead () from /usr/kde/3.5/lib/libkdecore.so.4
#13 0x00000009 in ?? ()
#14 0xa7778264 in ?? () from /usr/kde/3.5/lib/libkdecore.so.4
#15 0xa77286c4 in KNetwork::KClientSocketBase::slotReadActivity () from /usr/kde/3.5/lib/libkdecore.so.4
#16 0xa77286a6 in KNetwork::KClientSocketBase::slotReadActivity () from /usr/kde/3.5/lib/libkdecore.so.4
#17 0xa773ce45 in KNetwork::KClientSocketBase::qt_invoke () from /usr/kde/3.5/lib/libkdecore.so.4
#18 0x083083d0 in ?? ()
#19 0x082d0eb8 in ?? ()
#20 0xa72144db in QSocket::sn_read () from /usr/qt/3/lib/libqt-mt.so.3
#21 0xa702a4c2 in QObject::activate_signal () from /usr/qt/3/lib/libqt-mt.so.3
#22 0xa73509a0 in QSocketNotifier::activated () from /usr/qt/3/lib/libqt-mt.so.3
#23 0xa704748f in QSocketNotifier::event () from /usr/qt/3/lib/libqt-mt.so.3
#24 0xa6fcc8a7 in QApplication::internalNotify () from /usr/qt/3/lib/libqt-mt.so.3
#25 0xa6fcd501 in QApplication::notify () from /usr/qt/3/lib/libqt-mt.so.3
#26 0xa76f880c in KApplication::notify () from /usr/kde/3.5/lib/libkdecore.so.4
#27 0xafc2d820 in ?? ()
#28 0x0845b818 in ?? ()
#29 0xafc2d608 in ?? ()
#30 0xa72b42b9 in QRecursiveMutexPrivate::unlock () from /usr/qt/3/lib/libqt-mt.so.3
Previous frame inner to this frame (corrupt stack?)

edit, then again, I'm not so sure, I just "svn up"ed, and I seem to be at the latest revision, so its still freezing.

George wrote:If no more problems like this come up, we will release tomorrow.

Sorry George, i can't test it because i think my monitor died
(it's not responding at all when pressing the power button(yes i checked the cables))

I'll try solving it asap, i hope you've got testers enough.

EDIT
Solved, i'am on a 13 year old 15 inch monitor@ 1024 x 768 pixels now

Problem still present here, although it now happened while doing some things in GUI. (not sure if it's the DHT: refreshing bucket again)

(i did:
going to QM, hitting first torrent in download tab, then hit upload tab)

Tomasu wrote:I assume this will fix my dht freezing problems? I managed to attach gdb and grab a backtrace:

Code: Select all

#0  0xa7eb1d9f in std::_Rb_tree<unsigned char, std::pair<unsigned char const, dht::RPCCall*>, std::_Select1st<std::pair<unsigned char const, dht::RPCCall*> >, std::less<unsigned char>, std::allocator<std::pair<unsigned char const, dht::RPCCall*> > >::find () from /usr/kde/3.5/lib/libktorrent.so.0
#1  0xa7eb0ae0 in dht::RPCServer::doCall () from /usr/kde/3.5/lib/libktorrent.so.0
#2  0xa7ead3e5 in dht::KBucket::pingQuestionable () from /usr/kde/3.5/lib/libktorrent.so.0
#3  0xa7eadbd8 in dht::KBucket::onResponse () from /usr/kde/3.5/lib/libktorrent.so.0
#4  0xa7eafbec in dht::RPCCallListener::qt_invoke () from /usr/kde/3.5/lib/libktorrent.so.0
#5  0xa7029de9 in QObject::activate_signal () from /usr/qt/3/lib/libqt-mt.so.3
#6  0xa7eafcce in dht::RPCCall::onCallResponse () from /usr/kde/3.5/lib/libktorrent.so.0
#7  0xa7eafd68 in dht::RPCCall::response () from /usr/kde/3.5/lib/libktorrent.so.0
#8  0xa7eb1069 in dht::RPCServer::readPacket () from /usr/kde/3.5/lib/libktorrent.so.0
#9  0xa7eb12a2 in dht::RPCServer::qt_invoke () from /usr/kde/3.5/lib/libktorrent.so.0
#10 0xa7029de9 in QObject::activate_signal () from /usr/qt/3/lib/libqt-mt.so.3
#11 0xa702a5bd in QObject::activate_signal () from /usr/qt/3/lib/libqt-mt.so.3
#12 0xa772869a in KNetwork::KClientSocketBase::readyRead () from /usr/kde/3.5/lib/libkdecore.so.4
#13 0x00000009 in ?? ()
#14 0xa7778264 in ?? () from /usr/kde/3.5/lib/libkdecore.so.4
#15 0xa77286c4 in KNetwork::KClientSocketBase::slotReadActivity () from /usr/kde/3.5/lib/libkdecore.so.4
#16 0xa77286a6 in KNetwork::KClientSocketBase::slotReadActivity () from /usr/kde/3.5/lib/libkdecore.so.4
#17 0xa773ce45 in KNetwork::KClientSocketBase::qt_invoke () from /usr/kde/3.5/lib/libkdecore.so.4
#18 0x083083d0 in ?? ()
#19 0x082d0eb8 in ?? ()
#20 0xa72144db in QSocket::sn_read () from /usr/qt/3/lib/libqt-mt.so.3
#21 0xa702a4c2 in QObject::activate_signal () from /usr/qt/3/lib/libqt-mt.so.3
#22 0xa73509a0 in QSocketNotifier::activated () from /usr/qt/3/lib/libqt-mt.so.3
#23 0xa704748f in QSocketNotifier::event () from /usr/qt/3/lib/libqt-mt.so.3
#24 0xa6fcc8a7 in QApplication::internalNotify () from /usr/qt/3/lib/libqt-mt.so.3
#25 0xa6fcd501 in QApplication::notify () from /usr/qt/3/lib/libqt-mt.so.3
#26 0xa76f880c in KApplication::notify () from /usr/kde/3.5/lib/libkdecore.so.4
#27 0xafc2d820 in ?? ()
#28 0x0845b818 in ?? ()
#29 0xafc2d608 in ?? ()
#30 0xa72b42b9 in QRecursiveMutexPrivate::unlock () from /usr/qt/3/lib/libqt-mt.so.3
Previous frame inner to this frame (corrupt stack?)

edit, then again, I'm not so sure, I just "svn up"ed, and I seem to be at the latest revision, so its still freezing.

OK, this should be fixed now.

I think most issues here should be resolved in current SVN version.

Yep, no problems anymore and runs smoothly now.

OK, that's good, I think DHT is stable enough for a beta release tomorrow.