Bug 298313 - kontact crash when re-opening mail "stuck" in outbox
Summary: kontact crash when re-opening mail "stuck" in outbox
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: 4.8.2
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-17 16:50 UTC by Andreas K. Huettel
Modified: 2017-01-07 22:20 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (5.20 KB, text/plain)
2013-03-20 14:19 UTC, Lester Petrie
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas K. Huettel 2012-04-17 16:50:15 UTC
Application: kontact (4.8.2)
KDE Platform Version: 4.8.2 (4.8.2) (Compiled from sources)
Qt Version: 4.8.1
Operating System: Linux 3.2.2-hardened-r1 x86_64
Distribution (Platform): Gentoo Packages

-- Information about the crash:
- What I was doing when the application crashed:

Tried to send an e-mail to many recipients. One of the addresses was incorrect, and the mail server refused it, so it remained in the outbox. Doubleclicked on it to edit, and kontact crashed.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[Current thread is 1 (Thread 0x360b118c760 (LWP 31583))]

Thread 4 (Thread 0x3609690b700 (LWP 31584)):
#0  pthread_cond_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00000360ad77d8a4 in scavengerThread (this=0x360ae12aec0) at wtf/FastMalloc.cpp:2495
#2  WTF::TCMalloc_PageHeap::runScavengerThread (context=0x360ae12aec0) at wtf/FastMalloc.cpp:1618
#3  0x00000360a8b21c5c in start_thread (arg=0x3609690b700) at pthread_create.c:301
#4  0x00000360ae4889cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 3 (Thread 0x3609600a700 (LWP 31585)):
#0  0x00000360ae47fd13 in *__GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00000360a7947028 in g_main_context_poll (n_fds=1, fds=0x360900021f0, timeout=-1, context=0x36090000970, priority=<optimized out>) at gmain.c:3402
#2  g_main_context_iterate (context=0x36090000970, block=1, dispatch=1, self=<optimized out>) at gmain.c:3084
#3  0x00000360a7947531 in g_main_context_iteration (context=0x36090000970, may_block=1) at gmain.c:3152
#4  0x00000360af9f9e7f in QEventDispatcherGlib::processEvents (this=0x3c1be0d020, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:424
#5  0x00000360af9c1cd2 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#6  0x00000360af9c20b5 in QEventLoop::exec (this=0x36096009e10, flags=...) at kernel/qeventloop.cpp:204
#7  0x00000360af89c5f8 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#8  0x00000360af89f503 in QThreadPrivate::start (arg=0x3c1be0cb40) at thread/qthread_unix.cpp:298
#9  0x00000360a8b21c5c in start_thread (arg=0x3609600a700) at pthread_create.c:301
#10 0x00000360ae4889cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 2 (Thread 0x36082606700 (LWP 4010)):
#0  0x00000360ae482263 in select () at ../sysdeps/unix/syscall-template.S:82
#1  0x00000360af99a10c in QProcessManager::run (this=0x360afd35d40) at io/qprocess_unix.cpp:245
#2  0x00000360af89f503 in QThreadPrivate::start (arg=0x360afd35d40) at thread/qthread_unix.cpp:298
#3  0x00000360a8b21c5c in start_thread (arg=0x36082606700) at pthread_create.c:301
#4  0x00000360ae4889cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 1 (Thread 0x360b118c760 (LWP 31583)):
[KCrash Handler]
#6  QCoreApplication::postEvent (receiver=0x3c1e43ffb0, event=0x3c1e5b3370, priority=0) at kernel/qcoreapplication.cpp:1273
#7  0x00000360af9dbf56 in QObject::event (this=0x3c1e43ffb0, e=<optimized out>) at kernel/qobject.cpp:1195
#8  0x00000360aec3ca64 in QApplicationPrivate::notify_helper (this=0x3c1bc3ff70, receiver=0x3c1e43ffb0, e=0x3c1f97fa50) at kernel/qapplication.cpp:4554
#9  0x00000360aec41c2b in QApplication::notify (this=<optimized out>, receiver=0x3c1e43ffb0, e=0x3c1f97fa50) at kernel/qapplication.cpp:4415
#10 0x00000360b04ecb66 in KApplication::notify (this=0x3cb08df6240, receiver=0x3c1e43ffb0, event=0x3c1f97fa50) at /opt/virtual/tmp-portage/portage/kde-base/kdelibs-4.8.2/work/kdelibs-4.8.2/kdeui/kernel/kapplication.cpp:311
#11 0x00000360af9c31eb in QCoreApplication::notifyInternal (this=0x3cb08df6240, receiver=0x3c1e43ffb0, event=0x3c1f97fa50) at kernel/qcoreapplication.cpp:876
#12 0x00000360af9c70a7 in sendEvent (event=0x3c1f97fa50, receiver=0x3c1e43ffb0) at kernel/qcoreapplication.h:231
#13 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x3c1bc0bb40) at kernel/qcoreapplication.cpp:1500
#14 0x00000360af9f9c87 in sendPostedEvents () at kernel/qcoreapplication.h:236
#15 postEventSourceDispatch (s=<optimized out>) at kernel/qeventdispatcher_glib.cpp:279
#16 0x00000360a7946ada in g_main_dispatch (context=0x3c1bc428e0) at gmain.c:2441
#17 g_main_context_dispatch (context=0x3c1bc428e0) at gmain.c:3011
#18 0x00000360a7947308 in g_main_context_iterate (context=0x3c1bc428e0, block=1, dispatch=1, self=<optimized out>) at gmain.c:3089
#19 0x00000360a7947531 in g_main_context_iteration (context=0x3c1bc428e0, may_block=1) at gmain.c:3152
#20 0x00000360af9f9e7f in QEventDispatcherGlib::processEvents (this=0x3c1bc368b0, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:424
#21 0x00000360aecfb526 in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=<optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#22 0x00000360af9c1cd2 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#23 0x00000360af9c20b5 in QEventLoop::exec (this=0x3cb08df6170, flags=...) at kernel/qeventloop.cpp:204
#24 0x00000360af9c758b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148
#25 0x0000003c1ba0292a in main (argc=1, argv=0x3cb08df6868) at /opt/virtual/tmp-portage/portage/kde-base/kontact-4.8.2/work/kontact-4.8.2/kontact/src/main.cpp:218

Possible duplicates by query: bug 294900, bug 290710, bug 288638, bug 286847, bug 286846.

Reported using DrKonqi
Comment 1 Lester Petrie 2013-03-20 14:19:08 UTC
Created attachment 78240 [details]
New crash information added by DrKonqi

kontact (4.9.5) on KDE Platform 4.9.5 using Qt 4.8.4

- What I was doing when the application crashed:

I had clicked on an attachment to view it, and view only showed it as an icon. So I closed view, and right clicked on the attachment icon to open it in something else.  Kontact crashed at that point.  I compared my backtrace with the original, and, at least to me, they don't look the same.

-- Backtrace (Reduced):
#6  QCoreApplication::postEvent (receiver=0x354d5b0, event=0x377e4a0, priority=0) at kernel/qcoreapplication.cpp:1343
#7  0x000000395ab8c29e in QObject::event (this=0x354d5b0, e=<optimized out>) at kernel/qobject.cpp:1194
#8  0x000000395c3ca5ac in QApplicationPrivate::notify_helper (this=this@entry=0x1857d50, receiver=receiver@entry=0x354d5b0, e=e@entry=0x36df210) at kernel/qapplication.cpp:4562
#9  0x000000395c3cea2a in QApplication::notify (this=0x7fff39c082f0, receiver=0x354d5b0, e=0x36df210) at kernel/qapplication.cpp:4423
#10 0x0000003497a468c6 in KApplication::notify (this=0x7fff39c082f0, receiver=0x354d5b0, event=0x36df210) at /usr/src/debug/kdelibs-4.9.5/kdeui/kernel/kapplication.cpp:311
Comment 2 Denis Kurz 2016-09-24 19:25:39 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kontact (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 3 Denis Kurz 2017-01-07 22:20:55 UTC
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.