Summary: | Kmail2 crash when reading emails at start of day | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | Denis <Denis.Leslie> |
Component: | Mixed Maildir resource | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | crash | CC: | Denis.Leslie, krammer |
Priority: | NOR | ||
Version: | 4.10 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
Denis
2013-07-04 09:08:12 UTC
Created attachment 80959 [details]
New crash information added by DrKonqi
akonadi_mixedmaildir_resource (4.10) on KDE Platform 4.10.3 "release 1" using Qt 4.8.4
- What I was doing when the application crashed:
I had typed a reply to an email and clicked "Send" to send it to 3 recipients.
Kmail2 crashed, and all the folder names under KMail Folders turned red.
-- Backtrace (Reduced):
#7 0x00007f47676ce138 in memmove (__len=18446744073709513475, __src=<optimized out>, __dest=0x7f475c88087c) at /usr/include/bits/string3.h:57
#8 KMBox::MBox::purge (this=0x2181068, deletedEntries=..., movedEntries=0x7fffdc8299d0) at /usr/src/debug/kdepimlibs-4.10.3/kmbox/mbox.cpp:386
#9 0x0000000000435545 in purge (movedEntries=..., this=0x2181050) at /usr/src/debug/kdepim-runtime-4.10.3/resources/mixedmaildir/mixedmaildirstore.cpp:174
#10 MixedMaildirStore::Private::visit (this=0x218ddb0, job=0x320e630) at /usr/src/debug/kdepim-runtime-4.10.3/resources/mixedmaildir/mixedmaildirstore.cpp:2196
#11 0x00000000004221c9 in MixedMaildirStore::processJob (this=<optimized out>, job=0x320e630) at /usr/src/debug/kdepim-runtime-4.10.3/resources/mixedmaildir/mixedmaildirstore.cpp:2287
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present? If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months. Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input. |