Bug 340207 - Kontact crash on start-up
Summary: Kontact crash on start-up
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2014-10-21 18:00 UTC by sebastiaan.vandenbore
Modified: 2017-01-07 21:42 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
New crash information added by DrKonqi (2.65 KB, text/plain)
2014-10-27 09:46 UTC, sebastiaan.vandenbore
Details

Note You need to log in before you can comment on or make changes to this bug.
Description sebastiaan.vandenbore 2014-10-21 18:00:42 UTC
Application: kontact (4.12.5)
KDE Platform Version: 4.12.5 (Compiled from sources)
Qt Version: 4.8.5
Operating System: Linux 3.14.14-gentoo x86_64
Distribution (Platform): Gentoo Packages

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

Waiting for kontact to launch, no other desktop apps running.
Always starts with "Summary" module.

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 0x7fc8cdd07780 (LWP 31842))]

Thread 4 (Thread 0x7fc8b5cc6700 (LWP 31843)):
#0  0x00007fc8c5b7344c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007fc8c8bc4fed in WTF::TCMalloc_PageHeap::scavengerThread (this=0x7fc8c957c300 <WTF::pageheap_memory>) at wtf/FastMalloc.cpp:2495
#2  0x00007fc8c8bc50f9 in WTF::TCMalloc_PageHeap::runScavengerThread (context=<optimized out>) at wtf/FastMalloc.cpp:1618
#3  0x00007fc8c5b6f1da in start_thread () from /lib64/libpthread.so.0
#4  0x00007fc8cb266d7d in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7fc8b53c5700 (LWP 31844)):
#0  0x00007fc8cb25d29d in poll () from /lib64/libc.so.6
#1  0x00007fc8c4f507dc in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x00007fc8c4f50904 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#3  0x00007fc8cc662f3e in QEventDispatcherGlib::processEvents (this=0x7fc8b00008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#4  0x00007fc8cc63381f in QEventLoop::processEvents (this=this@entry=0x7fc8b53c4e70, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007fc8cc633aa8 in QEventLoop::exec (this=this@entry=0x7fc8b53c4e70, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007fc8cc536300 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:536
#7  0x00007fc8cc538a7c in QThreadPrivate::start (arg=0x10b4f50) at thread/qthread_unix.cpp:338
#8  0x00007fc8c5b6f1da in start_thread () from /lib64/libpthread.so.0
#9  0x00007fc8cb266d7d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7fc857fff700 (LWP 11972)):
#0  0x00007fc8c5b7344c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007fc86cf3f5c7 in QTWTF::TCMalloc_PageHeap::scavengerThread (this=0x7fc86d24c660 <QTWTF::pageheap_memory>) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359
#2  0x00007fc86cf3f5f9 in QTWTF::TCMalloc_PageHeap::runScavengerThread (context=<optimized out>) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464
#3  0x00007fc8c5b6f1da in start_thread () from /lib64/libpthread.so.0
#4  0x00007fc8cb266d7d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7fc8cdd07780 (LWP 31842)):
[KCrash Handler]
#6  QString (other=..., this=0x7fff8b9514d0) at /usr/include/qt4/QtCore/qstring.h:725
#7  KontactInterface::Plugin::identifier (this=0x9c25f24) at /var/tmp/portage/kde-base/kdepimlibs-4.12.5/work/kdepimlibs-4.12.5/kontactinterface/plugin.cpp:103
#8  0x00007fc8cd4f7c04 in Kontact::MainWindow::activateInitialPluginModule() () from /usr/lib64/libkontactprivate.so.4
#9  0x000000000040434a in _start ()

The reporter indicates this bug may be a duplicate of or related to bug 298328.

Possible duplicates by query: bug 324131, bug 322264, bug 320449, bug 315612, bug 313028.

Reported using DrKonqi
Comment 1 sebastiaan.vandenbore 2014-10-27 09:46:45 UTC
Created attachment 89334 [details]
New crash information added by DrKonqi

kontact (4.12.5) on KDE Platform 4.12.5 using Qt 4.8.5

- What I was doing when the application crashed:  I added filters, updated some local folders and tagged a bunch of email as spam.
I use spamassassin, razor and dcc for spam detection.

-- Backtrace (Reduced):
#6  QString (other=<error reading variable: Cannot access memory at address 0x732061206f74207e>, this=0x7fff58538490) at /usr/include/qt4/QtCore/qstring.h:725
#7  KontactInterface::Plugin::identifier (this=0x732061206f74206e) at /var/tmp/portage/kde-base/kdepimlibs-4.12.5/work/kdepimlibs-4.12.5/kontactinterface/plugin.cpp:103
#8  0x00007f7d6bffac04 in Kontact::MainWindow::activateInitialPluginModule() () from /usr/lib64/libkontactprivate.so.4
#9  0x000000000040434a in _start ()
Comment 2 Denis Kurz 2016-09-24 19:30:17 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 21:42:45 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.