Summary: | Kmail crashed on reply | ||
---|---|---|---|
Product: | [Applications] kontact | Reporter: | raphanne <raphaeljodeau> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | abulak, am.herrmann, anonymous.email.dropbox, carlo.tognetti, davidkintana, jussi01, kdebug, shaunteasdale+kde |
Priority: | NOR | Keywords: | triaged |
Version: | 4.10.2 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi |
Description
raphanne
2013-05-07 12:56:31 UTC
Created attachment 79897 [details]
New crash information added by DrKonqi
kontact (4.10.2) on KDE Platform 4.10.2 using Qt 4.8.4
- What I was doing when the application crashed:
I was simply replaing to one received e-mail
-- Backtrace (Reduced):
#6 0x00007f67de79b037 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#7 0x00007f67de79e698 in __GI_abort () at abort.c:90
[...]
#9 0x00007f67de7e4a46 in malloc_printerr (ptr=0x6340a70, str=0x7f67de8eba00 "free(): invalid next size (fast)", action=3) at malloc.c:4902
#10 _int_free (av=<optimized out>, p=0x6340a60, have_lock=0) at malloc.c:3758
#11 0x00007f67df259145 in free (alignment=8, x=<optimized out>) at ../../include/QtCore/../../src/corelib/tools/qvector.h:99
Created attachment 79898 [details]
New crash information added by DrKonqi
kontact (4.10.2) on KDE Platform 4.10.2 using Qt 4.8.4
- What I was doing when the application crashed:
I can confirm that the issue happens every time I try to reply to a received e-mail
-- Backtrace (Reduced):
#6 0x00007f1dbb21c037 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#7 0x00007f1dbb21f698 in __GI_abort () at abort.c:90
[...]
#9 0x00007f1dbb265a46 in malloc_printerr (ptr=0x64a8780, str=0x7f1dbb36c990 "double free or corruption (out)", action=3) at malloc.c:4902
#10 _int_free (av=<optimized out>, p=0x64a8770, have_lock=0) at malloc.c:3758
#11 0x00007f1dbc622488 in QString::free (d=0x64a8780) at tools/qstring.cpp:1235
*** Bug 320040 has been marked as a duplicate of this bug. *** Created attachment 80100 [details]
New crash information added by DrKonqi
kontact (4.10.2) on KDE Platform 4.10.2 using Qt 4.8.4
- What I was doing when the application crashed:
I just clicked to replay to an e-mail sent via Lotus Domino
The crack happens every time I try to reply to meils sent by the same user
-- Backtrace (Reduced):
#7 operator= (v=..., this=0x6560b90) at ../../include/QtCore/../../src/corelib/tools/qvector.h:394
#8 clear (this=0x6560b90) at ../../include/QtCore/../../src/corelib/tools/qvector.h:348
#9 QTextEngine::clearLineData (this=0x6560b90) at text/qtextengine.cpp:1483
#10 0x00007f1e39107a48 in QTextLayout::clearLayout (this=<optimized out>) at text/qtextlayout.cpp:658
#11 0x00007f1e39119acc in QTextBlock::clearLayout (this=this@entry=0x7fff84bfc7d0) at text/qtextobject.cpp:1084
*** Bug 320344 has been marked as a duplicate of this bug. *** *** Bug 318507 has been marked as a duplicate of this bug. *** *** Bug 318426 has been marked as a duplicate of this bug. *** Created attachment 83579 [details]
New crash information added by DrKonqi
kontact (4.11.3) on KDE Platform 4.11.3 using Qt 4.8.5
- What I was doing when the application crashed:
Replaying to a message containing html in inbox (offline imap)
-- Backtrace (Reduced):
#5 0x00007faca4213ec5 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#6 0x00007faca4215348 in __GI_abort () at abort.c:91
[...]
#8 0x00007faca42588f6 in malloc_printerr (action=3, str=0x7faca4345728 "free(): invalid next size (fast)", ptr=<optimized out>) at malloc.c:5007
#9 0x00007faca49a1705 in QTextEngine::clearLineData() () from /usr/lib64/qt4/libQtGui.so.4
[...]
#12 0x00007faca4b92526 in QTextEdit::resizeEvent(QResizeEvent*) () from /usr/lib64/qt4/libQtGui.so.4
Created attachment 85143 [details]
New crash information added by DrKonqi
kontact (4.8.5) on KDE Platform 4.8.5 (4.8.5) using Qt 4.8.1
- What I was doing when the application crashed:
I was "replying to all" to an HTL formated eMail. It doesn't happen every time I reply to all, but with this eMail allways crashes.
-- Backtrace (Reduced):
#6 0x00007f675120e425 in __GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7 0x00007f6751211b8b in __GI_abort () at abort.c:91
[...]
#9 0x00007f6751256b96 in malloc_printerr (action=3, str=0x7f6751356910 "free(): invalid next size (fast)", ptr=<optimized out>) at malloc.c:5039
#10 0x00007f675266eb78 in operator= (v=..., this=0x5de49e0) at ../../include/QtCore/../../src/corelib/tools/qvector.h:395
#11 clear (this=0x5de49e0) at ../../include/QtCore/../../src/corelib/tools/qvector.h:348
*** Bug 343166 has been marked as a duplicate of this bug. *** Created attachment 95013 [details]
New crash information added by DrKonqi
kmail (4.14.2) on KDE Platform 4.14.2 using Qt 4.8.6
- What I was doing when the application crashed:
tried to REPLY to an email
Kmail immediately crashed
Bug was repeated when Kmail restarted.
-- Backtrace (Reduced):
#6 0x00007f0e64200cc9 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#7 0x00007f0e642040d8 in __GI_abort () at abort.c:89
[...]
#9 0x00007f0e6424966e in malloc_printerr (ptr=<optimized out>, str=0x7f0e6434bcc8 "free(): invalid next size (fast)", action=1) at malloc.c:4996
#10 _int_free (av=<optimized out>, p=<optimized out>, have_lock=0) at malloc.c:3840
#11 0x00007f0e653aa48d in free (alignment=8, x=<optimized out>) at ../../include/QtCore/../../src/corelib/tools/qvector.h:99
This bug has never been confirmed for a Kontact version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those 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. (In reply to Denis Kurz from comment #12) > This bug has never been confirmed for a Kontact version that is based on KDE > Frameworks, except possibly a Technology Preview version 5.0.x. Those > 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. Feel free to close it now Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |