Bug 205986 - Kontact crashed, backtrace provided
Summary: Kontact crashed, backtrace provided
Status: RESOLVED DUPLICATE of bug 200137
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-02 14:19 UTC by Peter Popov
Modified: 2009-09-02 14:32 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Popov 2009-09-02 14:19:43 UTC
Application that crashed: kontact
Version of the application: 4.3.1
KDE Version: 4.3.1 (KDE 4.3.1)
Qt Version: 4.5.2
Operating System: Linux 2.6.30-020630-generic x86_64
Distribution: Ubuntu 9.04

What I was doing when the application crashed:
It was running in the background with the KMail component, can't say what it was doing at the time of the crash. I suppose it was checking mail as I have auto-retrieve set to 1 minute. The backtrace seems to point to either filters (of which I have LOTS) or search folders (of which I don't have any, but used to).

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#5  KMail::FolderJob::msgList (this=0x31) at /usr/include/qt4/QtCore/qlist.h:111
#6  0x00007f82f0179055 in FolderStorage::ignoreJobsForMessage (this=0x2da6c10, msg=0xbf3b5f0) at /build/buildd/kdepim-4.3.1/kmail/folderstorage.cpp:1113
#7  0x00007f82f0177f51 in FolderStorage::unGetMsg (this=0x2da6c10, idx=0) at /build/buildd/kdepim-4.3.1/kmail/folderstorage.cpp:569
#8  0x00007f82f01c1000 in KMSearchPattern::matches (this=0x4eb7160, serNum=<value optimized out>, ignoreBody=<value optimized out>) at /build/buildd/kdepim-4.3.1/kmail/kmsearchpattern.cpp:796
#9  0x00007f82f01779c9 in FolderStorage::slotProcessNextSearchBatch (this=0x2da6c10) at /build/buildd/kdepim-4.3.1/kmail/folderstorage.cpp:1180
#10 0x00007f82f035de13 in KMSearch::slotProcessNextBatch (this=0x4ea7910) at /build/buildd/kdepim-4.3.1/kmail/kmfoldersearch.cpp:272
#11 0x00007f82f035df88 in KMSearch::qt_metacall (this=0x4ea7910, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff39e6fb10)
    at /build/buildd/kdepim-4.3.1/obj-x86_64-linux-gnu/kmail/kmfoldersearch.moc:79
#12 0x00007f830318cea2 in QMetaObject::activate (sender=0x2d24760, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x8a9d920) at kernel/qobject.cpp:3113
#13 0x00007f8303187263 in QObject::event (this=0x2d24760, e=0x31) at kernel/qobject.cpp:1075
#14 0x00007f8303cf7f4d in QApplicationPrivate::notify_helper (this=0x2499170, receiver=0x2d24760, e=0x7fff39e701c0) at kernel/qapplication.cpp:4056
#15 0x00007f8303d0018a in QApplication::notify (this=0x7fff39e70510, receiver=0x2d24760, e=0x7fff39e701c0) at kernel/qapplication.cpp:4021
#16 0x00007f83050fcdeb in KApplication::notify (this=0x7fff39e70510, receiver=0x2d24760, event=0x7fff39e701c0) at /build/buildd/kde4libs-4.3.1/kdeui/kernel/kapplication.cpp:302
#17 0x00007f83031776ac in QCoreApplication::notifyInternal (this=0x7fff39e70510, receiver=0x2d24760, event=0x7fff39e701c0) at kernel/qcoreapplication.cpp:610
#18 0x00007f83031a4516 in QTimerInfoList::activateTimers (this=0x2489d30) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#19 0x00007f83031a0b2d in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:165
#20 0x00007f82fc8c820a in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#21 0x00007f82fc8cb8e0 in ?? () from /usr/lib/libglib-2.0.so.0
#22 0x00007f82fc8cba7c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#23 0x00007f83031a0a8f in QEventDispatcherGlib::processEvents (this=0x24610a0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#24 0x00007f8303d90bdf in QGuiEventDispatcherGlib::processEvents (this=0x7fff39e6f8b0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#25 0x00007f8303175f42 in QEventLoop::processEvents (this=<value optimized out>, flags={i = 971441200}) at kernel/qeventloop.cpp:149
#26 0x00007f8303176314 in QEventLoop::exec (this=0x7fff39e70470, flags={i = 971441280}) at kernel/qeventloop.cpp:201
#27 0x00007f83031785e4 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#28 0x0000000000404945 in main (argc=1, argv=0x7fff39e70bf8) at /build/buildd/kdepim-4.3.1/kontact/src/main.cpp:218

This bug may be a duplicate of or related to bug 205451

Reported using DrKonqi
Comment 1 Peter Popov 2009-09-02 14:28:14 UTC
Correction. I thought I had deleted my search folders, but apparently some of them came back after the previous crash. This puts my suspicion on search folders as Kontact really started crashing after I started using them. There is ONE search folder which scans the Inbox with subfolders (a total of about 3000 messages) for ("Message status" IS "Action item") AND ("Message status" IS NOT "Replied").

> What I was doing when the application crashed:
> It was running in the background with the KMail component, can't say what it
> was doing at the time of the crash. I suppose it was checking mail as I have
> auto-retrieve set to 1 minute. The backtrace seems to point to either filters
> (of which I have LOTS) or search folders (of which I don't have any, but used
> to).
Comment 2 Dario Andres 2009-09-02 14:32:10 UTC
Merging with bug 200137. Thanks

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