Bug 313825 - Kontact crashes when replying to an email
Summary: Kontact crashes when replying to an email
Status: RESOLVED WORKSFORME
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: 4.9.5
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-24 12:52 UTC by Rob
Modified: 2015-12-27 00:08 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
New crash information added by DrKonqi (16.72 KB, text/plain)
2013-09-20 14:46 UTC, Joshua Hatzenbuehler 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Rob 2013-01-24 12:52:22 UTC 
Application: kontact (4.9.5)
KDE Platform Version: 4.9.5
Qt Version: 4.8.2
Operating System: Linux 3.2.0-36-lowlatency x86_64
Distribution: KXStudio 12.04.1

-- Information about the crash:
- What I was doing when the application crashed: Every time I click REPLY on an old email in my inbox Kontact crashes shortly after the reply dialog box pops up.

The crash can be reproduced every time.

-- Backtrace:
Application: Kontact (kontact), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fecafa6d7c0 (LWP 8270))]

Thread 3 (Thread 0x7fec94eb9700 (LWP 8280)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007fecac264dec in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x00007fecac264f19 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x00007feca7715e9a in start_thread (arg=0x7fec94eb9700) at pthread_create.c:308
#4  0x00007fecacf99cbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#5  0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7fec945b8700 (LWP 8281)):
#0  0x00007fecacf8c8bd in read () at ../sysdeps/unix/syscall-template.S:82
#1  0x00007feca72838cf in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007feca7248ba4 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007feca7248fd6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007feca7249164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007fecad70f906 in QEventDispatcherGlib::processEvents (this=0x7fec8c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#6  0x00007fecad6dee42 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#7  0x00007fecad6df097 in QEventLoop::exec (this=0x7fec945b7dc0, flags=...) at kernel/qeventloop.cpp:204
#8  0x00007fecad5de057 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#9  0x00007fecad5e107b in QThreadPrivate::start (arg=0x19dbad0) at thread/qthread_unix.cpp:307
#10 0x00007feca7715e9a in start_thread (arg=0x7fec945b8700) at pthread_create.c:308
#11 0x00007fecacf99cbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#12 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fecafa6d7c0 (LWP 8270)):
[KCrash Handler]
#6  0x00007fecacedc425 in __GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7  0x00007fecacedfb8b in __GI_abort () at abort.c:91
#8  0x00007fecacf1a39e in __libc_message (do_abort=2, fmt=0x7fecad024008 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:201
#9  0x00007fecacf24b96 in malloc_printerr (action=3, str=0x7fecad024168 "double free or corruption (out)", ptr=<optimized out>) at malloc.c:5007
#10 0x00007fecad6f0da3 in QMetaCallEvent::~QMetaCallEvent (this=0xbdc91d0, __in_chrg=<optimized out>) at kernel/qobject.cpp:511
#11 0x00007fecad6f0de9 in QMetaCallEvent::~QMetaCallEvent (this=0xbdc91d0, __in_chrg=<optimized out>) at kernel/qobject.cpp:518
#12 0x00007fecad6e40f3 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x199c380) at kernel/qcoreapplication.cpp:1555
#13 0x00007fecad70f473 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236
#14 postEventSourceDispatch (s=<optimized out>) at kernel/qeventdispatcher_glib.cpp:279
#15 0x00007feca7248d53 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x00007feca72490a0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x00007feca7249164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x00007fecad70f89f in QEventDispatcherGlib::processEvents (this=0x199dc10, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#19 0x00007fecae183cde in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#20 0x00007fecad6e458f in QCoreApplication::processEvents (flags=...) at kernel/qcoreapplication.cpp:1102
#21 0x00007fec4af98857 in Message::KMeditor::ensureCursorVisible (this=0xbb24340) at ../../messagecomposer/kmeditor.cpp:558
#22 0x00007fec4af988f0 in Message::KMeditor::setCursorPositionFromStart (this=0xbb24340, pos=4013) at ../../messagecomposer/kmeditor.cpp:495
#23 0x00007fec4af8532a in Message::ComposerViewBase::setMessage (this=0xbac3bd0, msg=...) at ../../messagecomposer/composerviewbase.cpp:186
#24 0x00007fec4b91be27 in KMComposeWin::setMessage (this=0x590d760, newMsg=..., lastSignState=<optimized out>, lastEncryptState=<optimized out>, mayAutoSign=true, allowDecryption=<optimized out>, isModified=false) at ../../kmail/kmcomposewin.cpp:1509
#25 0x00007fec4b91f484 in KMComposeWin::KMComposeWin (this=0x590d760, aMsg=..., lastSignState=false, lastEncryptState=false, context=<optimized out>, id=<optimized out>, textSelection=..., customTemplate=..., __in_chrg=<optimized out>, __vtt_parm=<optimized out>) at ../../kmail/kmcomposewin.cpp:458
#26 0x00007fec4b9203dd in KMComposeWin::create (msg=..., lastSignState=false, lastEncryptState=<optimized out>, context=KMail::Composer::Reply, identity=0, textSelection=..., customTemplate=...) at ../../kmail/kmcomposewin.cpp:171
#27 0x00007fec4b8b4ec4 in KMReplyCommand::execute (this=0xb709c20) at ../../kmail/kmcommands.cpp:854
#28 0x00007fec4b8b3e71 in KMCommand::slotPostTransfer (this=0xb709c20, result=KMCommand::OK) at ../../kmail/kmcommands.cpp:268
#29 0x00007fecad6f4761 in QMetaObject::activate (sender=0xb709c20, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fff5ded6630) at kernel/qobject.cpp:3547
#30 0x00007fec4b8b3c7e in KMCommand::messagesTransfered (this=<optimized out>, _t1=KMCommand::OK) at ./kmcommands.moc:117
#31 0x00007fec4b8b9321 in KMCommand::slotJobFinished (this=0xb709c20) at ../../kmail/kmcommands.cpp:378
#32 0x00007fecad6f4761 in QMetaObject::activate (sender=0xb6f0aa0, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fff5ded67f0) at kernel/qobject.cpp:3547
#33 0x00007fecadb6b4c2 in KJob::result (this=<optimized out>, _t1=0xb6f0aa0) at ./kjob.moc:208
#34 0x00007fecadb6b500 in KJob::emitResult (this=0xb6f0aa0) at ../../kdecore/jobs/kjob.cpp:318
#35 0x00007fecad6f9926 in QObject::event (this=0xb6f0aa0, e=<optimized out>) at kernel/qobject.cpp:1195
#36 0x00007fecae0db7b4 in notify_helper (e=0xb3c7850, receiver=0xb6f0aa0, this=0x19d2880) at kernel/qapplication.cpp:4556
#37 QApplicationPrivate::notify_helper (this=0x19d2880, receiver=0xb6f0aa0, e=0xb3c7850) at kernel/qapplication.cpp:4528
#38 0x00007fecae0e0583 in QApplication::notify (this=0x7fff5ded7180, receiver=0xb6f0aa0, e=0xb3c7850) at kernel/qapplication.cpp:4417
#39 0x00007fecaee167a6 in KApplication::notify (this=0x7fff5ded7180, receiver=0xb6f0aa0, event=0xb3c7850) at ../../kdeui/kernel/kapplication.cpp:311
#40 0x00007fecad6e030c in QCoreApplication::notifyInternal (this=0x7fff5ded7180, receiver=0xb6f0aa0, event=0xb3c7850) at kernel/qcoreapplication.cpp:915
#41 0x00007fecad6e40ea in sendEvent (event=0xb3c7850, receiver=0xb6f0aa0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#42 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x199c380) at kernel/qcoreapplication.cpp:1539
#43 0x00007fecad70f473 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236
#44 postEventSourceDispatch (s=<optimized out>) at kernel/qeventdispatcher_glib.cpp:279
#45 0x00007feca7248d53 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#46 0x00007feca72490a0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#47 0x00007feca7249164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#48 0x00007fecad70f89f in QEventDispatcherGlib::processEvents (this=0x199dc10, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#49 0x00007fecae183cde in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#50 0x00007fecad6dee42 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#51 0x00007fecad6df097 in QEventLoop::exec (this=0x7fff5ded7110, flags=...) at kernel/qeventloop.cpp:204
#52 0x00007fecad6e43e7 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1187
#53 0x00000000004035c9 in main (argc=1, argv=0x7fff5ded77a8) at ../../../kontact/src/main.cpp:219

Possible duplicates by query: bug 313782, bug 313509, bug 313188, bug 311589, bug 309216.

Reported using DrKonqi
Comment 1 Joshua Hatzenbuehler 2013-09-20 14:46:14 UTC 
Created attachment 82425 [details]
New crash information added by DrKonqi

kontact (4.11.1) on KDE Platform 4.11.1 using Qt 4.8.4

- What I was doing when the application crashed:
Click reply to email and the application crashed.

-- Backtrace (Reduced):
#6  0x00007f3ddfc67037 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#7  0x00007f3ddfc6a698 in __GI_abort () at abort.c:90
[...]
#9  0x00007f3ddfcb0a46 in malloc_printerr (ptr=0x2e17070, str=0x7f3ddfdb7a00 "free(): invalid next size (fast)", action=3) at malloc.c:4902
#10 _int_free (av=<optimized out>, p=0x2e17060, have_lock=0) at malloc.c:3758
#11 0x00007f3de10bd0d5 in free (alignment=8, x=<optimized out>) at ../../include/QtCore/../../src/corelib/tools/qvector.h:99
Comment 2 Russell Greene 2015-12-26 21:10:45 UTC 
Could you try upgrading to kontact 5.0.2 and see if the problem still exists?
Also, has this always happened or is this recent?
Comment 3 Myriam Schweingruber 2015-12-27 00:08:34 UTC 
(In reply to Russell Greene from comment #2)
> Could you try upgrading to kontact 5.0.2 and see if the problem still exists?
> Also, has this always happened or is this recent?

Thank you for testing, Russel. 
This is already not reproducible with KMail 4.14.2, so no need to jump to another version. I have sent several mails through Kontact, no crash so far.