Bug 185308 - occasional crash in kmail when viewing any message
Summary: occasional crash in kmail when viewing any message
Status: RESOLVED DUPLICATE of bug 180741
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-23 08:40 UTC by Ritesh Raj Sarraf
Modified: 2009-03-19 00:41 UTC (History)
1 user (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 2009-02-23 08:40:09 UTC
Version:            (using KDE 4.2.0)
OS:                Linux
Installed from:    Debian testing/unstable Packages

I occasionally get this crash when navigating through messages. The crash isn't tied to one type of message. It just happens occasionally.

Application: Kontact (kontact), signal SIGSEGV
[Current thread is 0 (LWP 9588)]

Thread 2 (Thread 0xb0229b90 (LWP 9676)):
#0  0xb7ef6424 in __kernel_vsyscall ()
#1  0xb6b2aab1 in select () from /lib/i686/cmov/libc.so.6
#2  0xb76c0670 in QProcessManager::run (this=0x8e7d858) at io/qprocess_unix.cpp:301
#3  0xb75f152e in QThreadPrivate::start (arg=0x8e7d858) at thread/qthread_unix.cpp:185
#4  0xb53cb4c0 in start_thread () from /lib/i686/cmov/libpthread.so.0
#5  0xb6b326de in clone () from /lib/i686/cmov/libc.so.6

Thread 1 (Thread 0xb4ad86c0 (LWP 9588)):
[KCrash Handler]
#6  0xb14ba5bb in KMReaderWin::parseMsg (this=0x956a748, aMsg=0xd013a08) at ../../kmail/kmreaderwin.cpp:1628
#7  0xb14a6e08 in KMReaderWin::displayMessage (this=0x956a748) at ../../kmail/kmreaderwin.cpp:1555
#8  0xb14a7020 in KMReaderWin::updateReaderWin (this=0x956a748) at ../../kmail/kmreaderwin.cpp:1495
#9  0xb14b56a0 in KMReaderWin::qt_metacall (this=0x956a748, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbf90f408) at ./kmreaderwin.moc:164
#10 0xb76f5be0 in QMetaObject::activate (sender=0x956a798, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3031
#11 0xb76f6962 in QMetaObject::activate (sender=0x956a798, m=0xb77c40c4, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3101
#12 0xb7730867 in QTimer::timeout (this=0x956a798) at .moc/release-shared/moc_qtimer.cpp:126
#13 0xb76fc58e in QTimer::timerEvent (this=0x956a798, e=0xbf90f89c) at kernel/qtimer.cpp:257
#14 0xb76f06bf in QObject::event (this=0x956a798, e=0xbf90f89c) at kernel/qobject.cpp:1120
#15 0xb6dd679c in QApplicationPrivate::notify_helper (this=0x8e732c0, receiver=0x956a798, e=0xbf90f89c) at kernel/qapplication.cpp:3803
#16 0xb6dde61e in QApplication::notify (this=0xbf90fd4c, receiver=0x956a798, e=0xbf90f89c) at kernel/qapplication.cpp:3393
#17 0xb7bbd77d in KApplication::notify (this=0xbf90fd4c, receiver=0x956a798, event=0xbf90f89c) at ../../kdeui/kernel/kapplication.cpp:307
#18 0xb76e10e1 in QCoreApplication::notifyInternal (this=0xbf90fd4c, receiver=0x956a798, event=0xbf90f89c) at kernel/qcoreapplication.cpp:587
#19 0xb770f041 in QTimerInfoList::activateTimers (this=0x8e7d264) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:209
#20 0xb770f2db in QEventDispatcherUNIX::processEvents (this=0x8e838e8, flags={i = -1081017588}) at kernel/qeventdispatcher_unix.cpp:893
#21 0xb6e70f06 in QEventDispatcherX11::processEvents (this=0x8e838e8, flags={i = -1081017528}) at kernel/qeventdispatcher_x11.cpp:148
#22 0xb76df7aa in QEventLoop::processEvents (this=0xbf90fbc0, flags={i = -1081017464}) at kernel/qeventloop.cpp:143
#23 0xb76df96a in QEventLoop::exec (this=0xbf90fbc0, flags={i = -1081017400}) at kernel/qeventloop.cpp:194
#24 0xb76e2025 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:845
#25 0xb6dd6617 in QApplication::exec () at kernel/qapplication.cpp:3331
#26 0x0804bdd2 in main (argc=1, argv=0xbf90ff44) at ../../../kontact/src/main.cpp:218
Comment 1 Jaime Torres 2009-02-23 16:28:04 UTC
Could be related to bug 182956 and 90% sure a dup of bug 180741.
Comment 2 Christophe Marin 2009-03-09 11:36:40 UTC

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