Bug 225880 - kontact crash while idle
Summary: kontact crash while idle
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: 1.12.4
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 229398 243637 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-02-08 04:01 UTC by Ritesh Raj Sarraf
Modified: 2012-08-19 11:06 UTC (History)
2 users (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 Ritesh Raj Sarraf 2010-02-08 04:01:11 UTC
Application that crashed: kontact
Version of the application: 4.3.4
KDE Version: 4.3.4 (KDE 4.3.4)
Qt Version: 4.5.3
Operating System: Linux 2.6.32-1-686 i686
Distribution: Debian GNU/Linux testing (squeeze)

What I was doing when the application crashed:
OS was under load as many resource hungry kde applications were run. kontact was idle and it crashed. Not sure if it can be reproduced again.

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#6  QMutex::lock (this=0x3e4) at thread/qmutex.cpp:152
#7  0xb702de97 in QCoreApplication::postEvent (receiver=0xf4728e0, event=0xbe10888, priority=0) at kernel/qcoreapplication.cpp:1020
#8  0xb702e15c in QCoreApplication::postEvent (receiver=0xf4728e0, event=0xbe10888) at kernel/qcoreapplication.cpp:973
#9  0xb703d637 in QObject::deleteLater (this=0xf4728e0) at kernel/qobject.cpp:2018
#10 0xb0b0285b in KMail::ImapJob::slotGetMessageResult (this=0xf4728e0, job=0xb55f720) at ../../kmail/imapjob.cpp:478
#11 0xb0b071af in KMail::ImapJob::qt_metacall (this=0xf4728e0, _c=QMetaObject::InvokeMetaMethod, _id=12, _a=0xbfcc7c4c) at ./imapjob.moc:82
#12 0xb7043303 in QMetaObject::activate (sender=0xb55f720, from_signal_index=7, to_signal_index=7, argv=0xbfcc7c4c) at kernel/qobject.cpp:3112
#13 0xb7043f42 in QMetaObject::activate (sender=0xb55f720, m=0xb735d888, local_signal_index=3, argv=0xbfcc7c4c) at kernel/qobject.cpp:3186
#14 0xb71faa33 in KJob::result (this=0xb55f720, _t1=0xb55f720) at ./kjob.moc:188
#15 0xb71faed9 in KJob::emitResult (this=0xb55f720) at ../../kdecore/jobs/kjob.cpp:304
#16 0xb5a6cb15 in KIO::SimpleJob::slotFinished (this=0xb55f720) at ../../kio/kio/job.cpp:477
#17 0xb5a6d473 in KIO::TransferJob::slotFinished (this=0xb55f720) at ../../kio/kio/job.cpp:948
#18 0xb5a69a03 in KIO::TransferJob::qt_metacall (this=0xb55f720, _c=QMetaObject::InvokeMetaMethod, _id=7, _a=0xbfcc7e88) at ./jobclasses.moc:343
#19 0xb7043303 in QMetaObject::activate (sender=0xa236e58, from_signal_index=8, to_signal_index=8, argv=0x0) at kernel/qobject.cpp:3112
#20 0xb7043f42 in QMetaObject::activate (sender=0xa236e58, m=0xb5c13b84, local_signal_index=4, argv=0x0) at kernel/qobject.cpp:3186
#21 0xb5b32707 in KIO::SlaveInterface::finished (this=0xa236e58) at ./slaveinterface.moc:165
#22 0xb5b364b7 in KIO::SlaveInterface::dispatch (this=0xa236e58, _cmd=104, rawdata=...) at ../../kio/kio/slaveinterface.cpp:175
#23 0xb5b32be7 in KIO::SlaveInterface::dispatch (this=0xa236e58) at ../../kio/kio/slaveinterface.cpp:91
#24 0xb5b24bcd in KIO::Slave::gotInput (this=0xa236e58) at ../../kio/kio/slave.cpp:322
#25 0xb5b270b3 in KIO::Slave::qt_metacall (this=0xa236e58, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbfcc8158) at ./slave.moc:76
#26 0xb7043303 in QMetaObject::activate (sender=0xc02e118, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3112
#27 0xb7043f42 in QMetaObject::activate (sender=0xc02e118, m=0xb5c104c0, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3186
#28 0xb5a30c07 in KIO::Connection::readyRead (this=0xc02e118) at ./connection.moc:86
#29 0xb5a32513 in KIO::ConnectionPrivate::dequeue (this=0xfd2df30) at ../../kio/kio/connection.cpp:82
#30 0xb5a328f6 in KIO::Connection::qt_metacall (this=0xc02e118, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x1058e318) at ./connection.moc:73
#31 0xb703cb0b in QMetaCallEvent::placeMetaCall (this=0xf3d50e8, object=0xc02e118) at kernel/qobject.cpp:477
#32 0xb703e5e0 in QObject::event (this=0xc02e118, e=0xf3d50e8) at kernel/qobject.cpp:1110
#33 0xb666da94 in QApplicationPrivate::notify_helper (this=0x916e710, receiver=0xc02e118, e=0xf3d50e8) at kernel/qapplication.cpp:4065
#34 0xb6675bee in QApplication::notify (this=0xbfcc89c4, receiver=0xc02e118, e=0xf3d50e8) at kernel/qapplication.cpp:3605
#35 0xb753662d in KApplication::notify (this=0xbfcc89c4, receiver=0xc02e118, event=0xf3d50e8) at ../../kdeui/kernel/kapplication.cpp:302
#36 0xb702e1eb in QCoreApplication::notifyInternal (this=0xbfcc89c4, receiver=0xc02e118, event=0xf3d50e8) at kernel/qcoreapplication.cpp:610
#37 0xb702ee2e in QCoreApplication::sendEvent (receiver=0x0, event_type=0, data=0x9147388) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#38 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x9147388) at kernel/qcoreapplication.cpp:1247
#39 0xb702f00d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1140
#40 0xb670e3fe in QCoreApplication::sendPostedEvents (this=0x91470d8, flags=...) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#41 QEventDispatcherX11::processEvents (this=0x91470d8, flags=...) at kernel/qeventdispatcher_x11.cpp:75
#42 0xb702c83a in QEventLoop::processEvents (this=0xbfcc8940, flags=...) at kernel/qeventloop.cpp:149
#43 0xb702cc82 in QEventLoop::exec (this=0xbfcc8940, flags=...) at kernel/qeventloop.cpp:201
#44 0xb702f0d9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#45 0xb666d917 in QApplication::exec () at kernel/qapplication.cpp:3525
#46 0x0804b4c6 in main (argc=3, argv=0xbfcc8bc4) at ../../../kontact/src/main.cpp:218

Reported using DrKonqi
Comment 1 Björn Ruberg 2010-08-07 18:22:02 UTC
*** Bug 243637 has been marked as a duplicate of this bug. ***
Comment 2 Björn Ruberg 2010-08-07 18:22:32 UTC
*** Bug 229398 has been marked as a duplicate of this bug. ***
Comment 3 Myriam Schweingruber 2012-08-19 11:06:46 UTC
Thank you for your report. Kmail1 is currently unmaintained and the code has changed sufficiently in Kmail2 so the backtraces are not really useful anymore. Should you experience the same crash in Kmail 4.8.5 or later, please open a new report for Kmail2. Thank you for your understanding