Bug 323148 - kontact crashed when system rebooting
Summary: kontact crashed when system rebooting
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: 4.10.5
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-03 18:06 UTC by Andrey
Modified: 2017-01-07 22:04 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (4.19 KB, text/plain)
2014-05-13 07:05 UTC, Maarten Bezemer
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Andrey 2013-08-03 18:06:37 UTC
Application: kontact (4.10.5)
KDE Platform Version: 4.10.5 (Compiled from sources)
Qt Version: 4.8.4
Operating System: Linux 3.11.0-rc3 x86_64
Distribution: "Gentoo Base System release 2.2"

-- Information about the crash:
- What I was doing when the application crashed:
reboot system
when plasma is shutdowningn — I get message that kontact crashed

The crash can be reproduced sometimes.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fc42bcc7780 (LWP 1394))]

Thread 3 (Thread 0x7fc42851f700 (LWP 1395)):
#0  pthread_cond_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x0000003fe637c8b4 in WTF::TCMalloc_PageHeap::scavengerThread (this=0x3fe6d9d280 <WTF::pageheap_memory>) at wtf/FastMalloc.cpp:2495
#2  0x0000003fe637c9c9 in WTF::TCMalloc_PageHeap::runScavengerThread (context=<optimized out>) at wtf/FastMalloc.cpp:1618
#3  0x00000030d060903a in start_thread (arg=0x7fc42851f700) at pthread_create.c:305
#4  0x00000030d02eab8d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 2 (Thread 0x7fc427c1e700 (LWP 1397)):
#0  0x00000030d02dd2cd in read () at ../sysdeps/unix/syscall-template.S:82
#1  0x00000030cee85f8f in read (__nbytes=16, __buf=0x7fc427c1dca0, __fd=<optimized out>) at /usr/include/bits/unistd.h:45
#2  g_wakeup_acknowledge (wakeup=0x8760c0) at gwakeup.c:212
#3  0x00000030cee4a548 in g_main_context_check (context=context@entry=0x7fc4200009a0, max_priority=2147483647, fds=fds@entry=0x7fc4200029c0, n_fds=n_fds@entry=1) at gmain.c:2980
#4  0x00000030cee4a992 in g_main_context_iterate (context=context@entry=0x7fc4200009a0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3143
#5  0x00000030cee4ab2c in g_main_context_iteration (context=0x7fc4200009a0, may_block=1) at gmain.c:3207
#6  0x0000003fddfac48e in QEventDispatcherGlib::processEvents (this=0x7fc4200008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#7  0x0000003fddf7c70f in QEventLoop::processEvents (this=this@entry=0x7fc427c1de70, flags=...) at kernel/qeventloop.cpp:149
#8  0x0000003fddf7c9f0 in QEventLoop::exec (this=0x7fc427c1de70, flags=...) at kernel/qeventloop.cpp:204
#9  0x0000003fdde7f360 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:542
#10 0x0000003fdde822dc in QThreadPrivate::start (arg=0x9c2f60) at thread/qthread_unix.cpp:338
#11 0x00000030d060903a in start_thread (arg=0x7fc427c1e700) at pthread_create.c:305
#12 0x00000030d02eab8d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 1 (Thread 0x7fc42bcc7780 (LWP 1394)):
[KCrash Handler]
#6  0x0000003fddf93c8d in QObject::~QObject (this=0x2cf54d0, __in_chrg=<optimized out>) at kernel/qobject.cpp:819
#7  0x0000003fddf94509 in QObject::~QObject (this=0x2cf54d0, __in_chrg=<optimized out>) at kernel/qobject.cpp:939
#8  0x000000000040390e in qDeleteAll<QList<KMainWindow*>::const_iterator> (end=..., begin=...) at /usr/include/qt4/QtCore/qalgorithms.h:322
#9  qDeleteAll<QList<KMainWindow*> > (c=...) at /usr/include/qt4/QtCore/qalgorithms.h:330
#10 main (argc=1, argv=0x7fffb5b43758) at /media/trash/system/portage/kde-base/kontact-4.10.5/work/kontact-4.10.5/kontact/src/main.cpp:220

This bug may be a duplicate of or related to bug 288141.

Possible duplicates by query: bug 307140, bug 304826.

Reported using DrKonqi
Comment 1 Maarten Bezemer 2014-05-13 07:05:33 UTC
Created attachment 86602 [details]
New crash information added by DrKonqi

kontact (4.13) on KDE Platform 4.13.0 using Qt 4.8.6

I closed kontact while the composer window, with an unfinished email, was still opened

-- Backtrace (Reduced):
#6  QObject::~QObject (this=0x11b347f0, __in_chrg=<optimized out>) at kernel/qobject.cpp:819
#7  0x00007f1b350f59a9 in QObject::~QObject (this=0x11b347f0, __in_chrg=<optimized out>) at kernel/qobject.cpp:939
#8  0x00000000004036a6 in qDeleteAll<QList<KMainWindow*>::const_iterator> (end=..., begin=...) at /usr/include/qt4/QtCore/qalgorithms.h:322
#9  qDeleteAll<QList<KMainWindow*> > (c=...) at /usr/include/qt4/QtCore/qalgorithms.h:330
#10 main (argc=1, argv=0x7fff5b093658) at ../../../kontact/src/main.cpp:220
Comment 2 Denis Kurz 2016-09-24 19:23:56 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:04:31 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.