Summary: | Kmail crashes when replying to specific email | ||
---|---|---|---|
Product: | [Applications] kontact | Reporter: | noucamp13 |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | crash | CC: | kdenis, noucamp13 |
Priority: | NOR | Keywords: | drkonqi |
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
noucamp13
2016-04-04 15:48:18 UTC
Created attachment 99923 [details]
New crash information added by DrKonqi
kontact (4.14.2) on KDE Platform 4.14.2 using Qt 4.8.6
- What I was doing when the application crashed:
Replying to email (IMAP). Although it may be unrelated, I have noticed that some of my IMAP accounts fail to synchronize after Kmail has been opened for several hours. This was not the case (this time) with the account I was replying from.
-- Backtrace (Reduced):
#6 0x00007f0f3f3c1c37 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#7 0x00007f0f3f3c5028 in __GI_abort () at abort.c:89
[...]
#9 0x00007f0f3f40a55e in malloc_printerr (ptr=<optimized out>, str=0x7f0f3f50c7e0 "double free or corruption (out)", action=1) at malloc.c:4996
#10 _int_free (av=<optimized out>, p=<optimized out>, have_lock=0) at malloc.c:3840
#11 0x00007f0f4082c929 in QTextOption::operator= (this=0x826aa50, o=...) at text/qtextoption.cpp:129
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those Framework-based versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the opportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it. Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life. Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input. |