Bug 144808 - program crashes after short while
Summary: program crashes after short while
Status: RESOLVED DUPLICATE of bug 144416
Alias: None
Product: ktorrent
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Joris Guisson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-29 01:45 UTC by Gaston Sanda
Modified: 2007-05-01 11:54 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Gaston Sanda 2007-04-29 01:45:10 UTC 
Version:           2.0.3 (using KDE 3.5.5, Debian Package 4:3.5.5a.dfsg.1-8 (4.0))
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.18-4-486

After a while running the program crashes, specially if the computer is iddle. I have been using Ktorrent for some time and this problem started a few days ago.
Comment 1 Tommi Tervo 2007-04-29 16:18:58 UTC 
Please paste backtrace, possible dupe of http://bugs.kde.org/show_bug.cgi?id=144813
Comment 2 Johan M 2007-05-01 08:37:38 UTC 
Have similar situation. Everything works fine but then it just crashes. Also have noted that it happens more often when computer is idle. The crash report might not be to much help but here it is:

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
  :
[Thread debugging using libthread_db enabled]
[New Thread -1233930576 (LWP 11014)]
[New Thread -1247114336 (LWP 11064)]
  :

[KCrash handler]
#6  0xb7eb9aeb in dht::ParseRsp () from /usr/lib/libktorrent.so.0
#7  0xb7ebaaa2 in dht::MakeRPCMsg () from /usr/lib/libktorrent.so.0
#8  0xb7ebab9f in dht::RPCServer::readPacket () from /usr/lib/libktorrent.so.0
#9  0xb7ebaf12 in dht::RPCServer::qt_invoke () from /usr/lib/libktorrent.so.0
#10 0xb6f54957 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#11 0xb6f553fc in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#12 0xb76cf50c in KNetwork::KClientSocketBase::readyRead ()
   from /usr/lib/libkdecore.so.4
#13 0xb76cf546 in KNetwork::KClientSocketBase::slotReadActivity ()
   from /usr/lib/libkdecore.so.4
#14 0xb76e2723 in KNetwork::KClientSocketBase::qt_invoke ()
   from /usr/lib/libkdecore.so.4
#15 0xb76e27c6 in KNetwork::KDatagramSocket::qt_invoke ()
   from /usr/lib/libkdecore.so.4
#16 0xb6f54957 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#17 0xb6f5526e in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#18 0xb72e1e27 in QSocketNotifier::activated () from /usr/lib/libqt-mt.so.3
#19 0xb6f77516 in QSocketNotifier::event () from /usr/lib/libqt-mt.so.3
#20 0xb6eebb88 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#21 0xb6eed9b7 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#22 0xb769bd62 in KApplication::notify () from /usr/lib/libkdecore.so.4
#23 0xb6e7e389 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#24 0xb6eddf81 in QEventLoop::activateSocketNotifiers ()
   from /usr/lib/libqt-mt.so.3
#25 0xb6e92ea7 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#26 0xb6f0625e in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#27 0xb6f0606e in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#28 0xb6eed731 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#29 0x08065efb in ?? ()
#30 0xb677f8cc in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#31 0x0805e301 in ?? ()
Comment 3 Joris Guisson 2007-05-01 11:54:38 UTC 
As we expected, a dupe, this bug has been fixed in 2.1.4

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