Summary: | Crash soon after startup after migration to 4.7.0 and Akonadi | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | Maarten ter Huurne <maarten> |
Component: | Mail Filter Agent | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | briank, maarten, montel |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 4.8 | |
Sentry Crash Report: | |||
Attachments: |
New crash information added by DrKonqi
Third backtrace, again similar but not the same |
Description
Maarten ter Huurne
2011-08-14 22:31:12 UTC
Created attachment 62828 [details]
New crash information added by DrKonqi
kontact (4.7.0) on KDE Platform 4.7.00 (4.7.0) "release 10" using Qt 4.7.3
I just got another crash with the same symptoms but different methods at the top of the stack trace. So I attached it in case it gives a better picture of what is wrong.
-- Backtrace (Reduced):
#6 ~QVector (x=0x75584c0) at ../../src/corelib/tools/qvector.h:119
#7 ~QRegionPrivate (x=0x75584c0) at painting/qregion.cpp:1085
#8 QRegion::cleanUp (x=0x75584c0) at painting/qregion.cpp:3904
#9 0x00007f1e797299d2 in QRegion::operator= (this=<value optimized out>, r=...) at painting/qregion.cpp:3928
#10 0x00007f1e79798be7 in QX11PaintEngine::begin (this=0xeb1d20, pdev=0x80cee8) at painting/qpaintengine_x11.cpp:504
Created attachment 62829 [details]
Third backtrace, again similar but not the same
Attached a third backtrace.
Is it normal to have a 400-level call stack or did recursion go wrong? MailCommon::SearchRuleString::matchesInternal is in this backtrace 13 times...
Workaround found: if I edit ~/.kde4/share/config/kmail2rc to remove all my filters, KMail seems to be stable. I waited until Akonadi had finished processing the contents of the maildirs and then re-added my filters 10 at a time (I have 44 in total). It seems to be stable now. So the bug might be some kind of race condition that occurs when new mails (from the point of view of KMail: the files are not new but their availability through Akonadi is) are coming in at a fast pace and there are a lot of filters defined. Or perhaps there is a problem if filters are moving mails to the same maildir folder that Akonadi is scanning. comment 2 : I fixed it in kmail-4.7.1 Don't know for other crash. *** Bug 287386 has been marked as a duplicate of this bug. *** I haven't had any more of these crashes in KDE 4.8 and 4.9. Thank you for the feedback. |