[Bug 215043] New: Crash during filtering of an IMAP account

mathieu.lopes at gmail.com mathieu.lopes at gmail.com
Tue Nov 17 22:14:20 GMT 2009


https://bugs.kde.org/show_bug.cgi?id=215043

           Summary: Crash during filtering of an IMAP account
           Product: kontact
           Version: unspecified
          Platform: Unlisted Binaries
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: general
        AssignedTo: kdepim-bugs at kde.org
        ReportedBy: mathieu.lopes at gmail.com


Application that crashed: kontact
Version of the application: 4.3.2
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-14-generic x86_64
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
I just set up several filtering rules in Kmail on an IMAP account, then i
started applying them all on 3000 messages, it crashed after treating 1000 of
them.

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
The current source language is "auto; currently c".
[KCrash Handler]
#5  0x00007fd47d9c3391 in KMSearchPattern::requiresBody (this=0x3e0d200) at
../../kmail/kmsearchpattern.cpp:809
#6  0x00007fd47d9c36a4 in KMSearchPattern::matches (this=0x3e0d200,
serNum=<value optimized out>, ignoreBody=false) at
../../kmail/kmsearchpattern.cpp:789
#7  0x00007fd47d9899ec in KMail::ActionScheduler::filterMessage
(this=0x26392d0) at ../../kmail/actionscheduler.cpp:641
#8  0x00007fd47d989cf4 in KMail::ActionScheduler::qt_metacall (this=0x26392d0,
_c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff61b0efc0)
at ./actionscheduler.moc:124
#9  0x00007fd492f0dddc in QMetaObject::activate (sender=0x26cc250,
from_signal_index=<value optimized out>, to_signal_index=<value optimized out>,
argv=0xc005) at kernel/qobject.cpp:3113
#10 0x00007fd492f07d83 in QObject::event (this=0x26cc250, e=0x0) at
kernel/qobject.cpp:1075
#11 0x00007fd493818efc in QApplicationPrivate::notify_helper (this=0x1009810,
receiver=0x26cc250, e=0x7fff61b0f5c0) at kernel/qapplication.cpp:4056
#12 0x00007fd4938201ce in QApplication::notify (this=0x7fff61b0f920,
receiver=0x26cc250, e=0x7fff61b0f5c0) at kernel/qapplication.cpp:4021
#13 0x00007fd49444fab6 in KApplication::notify (this=0x7fff61b0f920,
receiver=0x26cc250, event=0x7fff61b0f5c0) at
../../kdeui/kernel/kapplication.cpp:302
#14 0x00007fd492ef8c2c in QCoreApplication::notifyInternal
(this=0x7fff61b0f920, receiver=0x26cc250, event=0x7fff61b0f5c0) at
kernel/qcoreapplication.cpp:610
#15 0x00007fd492f23862 in QCoreApplication::sendEvent (this=0x1005c80) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#16 QTimerInfoList::activateTimers (this=0x1005c80) at
kernel/qeventdispatcher_unix.cpp:572
#17 0x00007fd492f2125d in timerSourceDispatch (source=<value optimized out>) at
kernel/qeventdispatcher_glib.cpp:165
#18 0x00007fd48c772bbe in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#19 0x00007fd48c776588 in ?? () from /lib/libglib-2.0.so.0
#20 0x00007fd48c7766b0 in g_main_context_iteration () from
/lib/libglib-2.0.so.0
#21 0x00007fd492f211a6 in QEventDispatcherGlib::processEvents (this=0xfd2cb0,
flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#22 0x00007fd4938ad4be in QGuiEventDispatcherGlib::processEvents (this=0x5ef,
flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#23 0x00007fd492ef7532 in QEventLoop::processEvents (this=<value optimized
out>, flags=) at kernel/qeventloop.cpp:149
#24 0x00007fd492ef7904 in QEventLoop::exec (this=0x7fff61b0f860, flags=) at
kernel/qeventloop.cpp:201
#25 0x00007fd492ef9ab9 in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:888
#26 0x0000000000403f47 in main (argc=<value optimized out>, argv=<value
optimized out>) at ../../../kontact/src/main.cpp:218

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

Reported using DrKonqi

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the Kdepim-bugs mailing list