[Konversation-devel] [Bug 145614] Konversation crashes at startup when receiving much data via bouncer

[Nils Kneuper]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=145614         




------- Additional Comments From crazy-ivanovic gmx net  2007-06-10 11:21 -------
Okay, today it crashed again and now it looks like I got something like a backtrace:

Short description of the prob (in german):
Das Programm Konversation (konversation) ist abgestürzt und hat das Signal 11 (SIGSEGV) veranlasst.

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1233353040 (LWP 4959)]
[KCrash handler]
#6  InputFilter::parseClientCommand (this=0x839a6bc, prefix= 0xbfac13fc, 
    command= 0xbfac13f8, parameterList= 0xbfac13f4, _trailing= 0xbfac1404)
    at inputfilter.cpp:153
#7  0x080dfbed in InputFilter::parseLine (this=0x839a6bc, 
    a_newLine= 0xbfac147c) at inputfilter.cpp:112
#8  0x08105309 in Server::processIncomingData (this=0x839a4f0)
    at server.cpp:1024
#9  0x08109044 in Server::qt_invoke (this=0x839a4f0, _id=54, _o=0xbfac1628)
    at server.moc:874
#10 0xb703503e in QObject::activate_signal (this=0x839a584, clist=0x83c6918, 
    o=0xbfac1628) at kernel/qobject.cpp:2356
#11 0xb7035b80 in QObject::activate_signal (this=0x839a584, signal=2)
    at kernel/qobject.cpp:2325
#12 0xb734a7f1 in QTimer::timeout (this=0x839a584)
    at .moc/release-shared-mt/moc_qtimer.cpp:82
#13 0xb70560be in QTimer::event (this=0x839a584, e=0xbfac18e4)
    at kernel/qtimer.cpp:219
#14 0xb6fd9f45 in QApplication::internalNotify (this=0xbfac1b04, 
    receiver=0x839a584, e=0xbfac18e4) at kernel/qapplication.cpp:2635
#15 0xb6fdaaa2 in QApplication::notify (this=0xbfac1b04, receiver=0x839a584, 
    e=0xbfac18e4) at kernel/qapplication.cpp:2358
#16 0xb76fdd34 in KApplication::notify (this=0xbfac1b04, receiver=0x839a584, 
    event=0xbfac18e4) at kapplication.cpp:550
#17 0xb6fcfcba in QEventLoop::activateTimers (this=0x825b688)
    at kernel/qapplication.h:496
#18 0xb6f8cd24 in QEventLoop::processEvents (this=0x825b688, flags=4)
    at kernel/qeventloop_x11.cpp:389
#19 0xb6fef8fd in QEventLoop::enterLoop (this=0x825b688)
    at kernel/qeventloop.cpp:198
#20 0xb6fef7a2 in QEventLoop::exec (this=0x825b688)
    at kernel/qeventloop.cpp:145
#21 0xb6fd9a6b in QApplication::exec (this=0xbfac1b04)
    at kernel/qapplication.cpp:2758
#22 0x0810fed9 in main (argc=3, argv=) at main.cpp:109


Like I already stated before: Now that I am using debug symbols and stuff it does not crash this often anymore. But the usual case is that chans are "lost" when attaching the bouncer. This means all the chans are shown for a short times and then some vanish again. To really have them shown I do have to close the connection to that "server" (my bouncer) and reconnect, then I do get all the chans as expected. I assume it is somehow connected to the way disconnects are handled because it only hapens when quite some data and a disconnect of the irc client come together (I am using the bouncer on a normal dsl line with a 24h disconnect).