KTorrent 3.2dev920084 (i.e., after RC1) crashed, again:

Code: Select all

Application: KTorrent (ktorrent), signal SIGABRT
[Thread debugging using libthread_db enabled]
[New Thread 0xb58138d0 (LWP 19166)]
[New Thread 0xb208cb90 (LWP 19483)]
[New Thread 0xb35c8b90 (LWP 19482)]
[New Thread 0xb40e2b90 (LWP 19177)]
[KCrash handler]
#6  0xb7f01430 in __kernel_vsyscall ()
#7  0xb5c50880 in raise () from /lib/tls/i686/cmov/libc.so.6
#8  0xb5c52248 in abort () from /lib/tls/i686/cmov/libc.so.6
#9  0xb7d7f0aa in QtMessageOutput (type=QtFatalMsg,
    msg=0xbfefffdc "QList: Out of memory")
    at .../libbtcore/util/log.cpp:305
#10 0xb6d10735 in qt_message_output () from /usr/lib/libQtCore.so.4
#11 0xb6d10872 in qFatal () from /usr/lib/libQtCore.so.4
#12 0xb6d3c4a6 in QListData::detach2 () from /usr/lib/libQtCore.so.4
#13 0x08084cb1 in QList<kt::ViewModel::Item*>::detach_helper (this=0xbff02088)
    at /usr/include/qt4/QtCore/qlist.h:516
#14 0x08083487 in kt::ViewModel::update (this=0x9d72b08, force_resort=false)
    at /usr/include/qt4/QtCore/qlist.h:107
#15 0x0807dc3d in kt::View::update (this=0x9cf26f8)
    at .../ktorrent/view.cpp:133
#16 0x0807538a in kt::GUI::update (this=0x97ca688)
    at .../ktorrent/gui.cpp:561
#17 0x08078562 in kt::GUI::qt_metacall (this=0x97ca688,
    _c=QMetaObject::InvokeMetaMethod, _id=22, _a=0xbff021b8)
    at .../build/ktorrent/gui.moc:133
#18 0xb6e1da60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#19 0xb6e1e7e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#20 0xb6e587a7 in QTimer::timeout () from /usr/lib/libQtCore.so.4
#21 0xb6e2440e in QTimer::timerEvent () from /usr/lib/libQtCore.so.4
#22 0xb6e1853f in QObject::event () from /usr/lib/libQtCore.so.4
#23 0xb63468ec in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#24 0xb634e72e in QApplication::notify () from /usr/lib/libQtGui.so.4
#25 0xb748cb2d in KApplication::notify () from /usr/lib/libkdeui.so.5
#26 0xb6e08e61 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#27 0xb6e36d81 in ?? () from /usr/lib/libQtCore.so.4
#28 0xb6e33520 in ?? () from /usr/lib/libQtCore.so.4
#29 0xb5a026f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#30 0xb5a05da3 in ?? () from /usr/lib/libglib-2.0.so.0
#31 0xb5a05f61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#32 0xb6e33478 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#33 0xb63e0ea5 in ?? () from /usr/lib/libQtGui.so.4
#34 0xb6e0752a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#35 0xb6e076ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#36 0xb6e09da5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#37 0xb6346767 in QApplication::exec () from /usr/lib/libQtGui.so.4
#38 0x080650a9 in main (argc=1, argv=0xbff02c64)
    at .../ktorrent/main.cpp:170
#0  0xb7f01430 in __kernel_vsyscall ()


This seems to be caused by the logger, writing out tens or hundreds of thousands of lines like this:

Code: Select all

Tue Feb 3 18:19:00 2009: Resetted chunk 42
...
Tue Feb 3 18:19:01 2009: Resetted chunk 22362


This may indicate an underlying issue, but perhaps the log level should just be limited? (Either way, it really shouldn't be crashing.) As far as I could find, there is no way to limit the log level right now (which was also discussed in this old topic).

mfb52 wrote:This seems to be caused by the logger, writing out tens or hundreds of thousands of lines like this:

Code: Select all

Tue Feb 3 18:19:00 2009: Resetted chunk 42
...
Tue Feb 3 18:19:01 2009: Resetted chunk 22362


The log viewer should limit the number of lines displayed to 200, I will see what is going wrong.

This may indicate an underlying issue, but perhaps the log level should just be limited? (Either way, it really shouldn't be crashing.) As far as I could find, there is no way to limit the log level right now

You can adjust the loglevel in the settings of the logviewer plugin.

Continuously printing messages to the log, does not increase the memory usage, so it can't be that.