Bug 277705 - KMail crashes if nepomuk is enabled
Summary: KMail crashes if nepomuk is enabled
Status: RESOLVED FIXED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.8.4
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 278944 289128 291293 299355 300203 301602 (view as bug list)
Depends on: 301453
Blocks:
  Show dependency treegraph
 
Reported: 2011-07-13 15:56 UTC by Unknown
Modified: 2013-02-02 14:53 UTC (History)
16 users (show)

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


Attachments
New crash information added by DrKonqi (10.10 KB, text/plain)
2012-06-08 12:47 UTC, Rex Dieter
Details
New crash information added by DrKonqi (5.36 KB, text/plain)
2012-06-08 20:20 UTC, François
Details
New crash information added by DrKonqi (9.21 KB, text/plain)
2012-06-12 11:37 UTC, K Woelfel
Details
New crash information added by DrKonqi (8.19 KB, text/plain)
2012-06-12 12:03 UTC, K Woelfel
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Unknown 2011-07-13 15:56:50 UTC
Application: kmail (2.1.96)
KDE Platform Version: 4.6.95 (4.7 RC2) "release 1"
Qt Version: 4.7.3
Operating System: Linux 2.6.37.6-0.5-desktop x86_64
Distribution: "openSUSE 11.4 (x86_64)"

-- Information about the crash:
Go to Options > Style (or something similar) > set the message pane to appear next to the message list. Hit Apply and click on a message in the list.
KMail crashes.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f2647111780 (LWP 8997))]

Thread 3 (Thread 0x7f262c4cf700 (LWP 9002)):
#0  0x00007f2644627c73 in select () at ../sysdeps/unix/syscall-template.S:82
#1  0x00007f2645bc996d in QProcessManager::run (this=0x7f2645f1cf80) at io/qprocess_unix.cpp:245
#2  0x00007f2645b00095 in QThreadPrivate::start (arg=0x7f2645f1cf80) at thread/qthread_unix.cpp:320
#3  0x00007f2644344a3f in start_thread (arg=0x7f262c4cf700) at pthread_create.c:297
#4  0x00007f264462e67d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#5  0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7f262a69c700 (LWP 9080)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007f2638b331d4 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/libQtWebKit.so.4
#2  0x00007f2644344a3f in start_thread (arg=0x7f262a69c700) at pthread_create.c:297
#3  0x00007f264462e67d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#4  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f2647111780 (LWP 8997)):
[KCrash Handler]
#6  deref (x=0xf241d0) at /usr/include/QtCore/qatomic_x86_64.h:133
#7  ~KSharedPtr (x=0xf241d0) at /usr/src/debug/kdelibs-4.6.95/kdecore/util/ksharedptr.h:90
#8  ~ParsingData (x=0xf241d0) at /usr/src/debug/kdelibs-4.6.95/kdecore/services/ktraderparse.cpp:41
#9  QThreadStorage<KTraderParse::ParsingData*>::deleteData (x=0xf241d0) at /usr/include/QtCore/qthreadstorage.h:133
#10 0x00007f2645afe612 in QThreadStorageData::set (this=0x16d9360, p=0x1780d00) at thread/qthreadstorage.cpp:165
#11 0x00007f26466fc837 in qThreadStorage_setLocalData<KTraderParse::ParsingData> (_constr=...) at /usr/include/QtCore/qthreadstorage.h:92
#12 setLocalData (_constr=...) at /usr/include/QtCore/qthreadstorage.h:148
#13 KTraderParse::parseConstraints (_constr=...) at /usr/src/debug/kdelibs-4.6.95/kdecore/services/ktraderparse.cpp:55
#14 0x00007f26466fc1d2 in KServiceTypeTrader::applyConstraints (lst=<value optimized out>, constraint=<value optimized out>) at /usr/src/debug/kdelibs-4.6.95/kdecore/services/kservicetypetrader.cpp:59
#15 0x00007f26466fc37b in KServiceTypeTrader::defaultOffers (this=<value optimized out>, serviceType=<value optimized out>, constraint=...) at /usr/src/debug/kdelibs-4.6.95/kdecore/services/kservicetypetrader.cpp:127
#16 0x00007f26466fc709 in KServiceTypeTrader::query (this=0xa2d3a0, serviceType=..., constraint=...) at /usr/src/debug/kdelibs-4.6.95/kdecore/services/kservicetypetrader.cpp:141
#17 0x00007f2636964296 in KEmoticonsPrivate::loadServiceList (this=0xee0930) at /usr/src/debug/kdelibs-4.6.95/kutils/kemoticons/kemoticons.cpp:71
#18 0x00007f26369643ea in KEmoticons::KEmoticons (this=0x17fd8a0) at /usr/src/debug/kdelibs-4.6.95/kutils/kemoticons/kemoticons.cpp:121
#19 0x00007f263dbd33e2 in operator-> (plainText=<value optimized out>, flags=11, maxUrlLen=<value optimized out>, maxAddressLen=<value optimized out>) at /usr/src/debug/kdepimlibs-4.6.95/kpimutils/linklocator.cpp:56
#20 KPIMUtils::LinkLocator::convertToHtml (plainText=<value optimized out>, flags=11, maxUrlLen=<value optimized out>, maxAddressLen=<value optimized out>) at /usr/src/debug/kdepimlibs-4.6.95/kpimutils/linklocator.cpp:426
#21 0x00007f263d71daa4 in MessageViewer::ObjectTreeParser::quotedHTML (this=0x7fff3229a360, s=..., decorate=<value optimized out>) at /usr/src/debug/kdepim-4.6.95/messageviewer/objecttreeparser.cpp:3175
#22 0x00007f263d728426 in MessageViewer::ObjectTreeParser::writeBodyStr (this=0x7fff3229a360, aStr=<value optimized out>, aCodec=0x618020, fromAddress=..., inlineSignatureState=@0x7fff32299f0c, inlineEncryptionState=@0x7fff32299f08, decorate=true) at /usr/src/debug/kdepim-4.6.95/messageviewer/objecttreeparser.cpp:3028
#23 0x00007f263d728aa3 in MessageViewer::ObjectTreeParser::writeBodyString (this=0x7fff3229a360, bodyString=..., fromAddress=..., codec=0x618020, result=..., decorate=true) at /usr/src/debug/kdepim-4.6.95/messageviewer/objecttreeparser.cpp:2115
#24 0x00007f263d7303a1 in MessageViewer::ObjectTreeParser::processTextPlainSubtype (this=0x7fff3229a360, curNode=0x987550, result=...) at /usr/src/debug/kdepim-4.6.95/messageviewer/objecttreeparser.cpp:1373
#25 0x00007f263d729636 in MessageViewer::ObjectTreeParser::parseObjectTreeInternal (this=0x7fff3229a360, node=0x987550) at /usr/src/debug/kdepim-4.6.95/messageviewer/objecttreeparser.cpp:335
#26 0x00007f263d729e85 in MessageViewer::ObjectTreeParser::stdChildHandling (this=0x7fff3229a640, child=0x987550) at /usr/src/debug/kdepim-4.6.95/messageviewer/objecttreeparser.cpp:1388
#27 0x00007f263d72a312 in MessageViewer::ObjectTreeParser::processMultiPartMixedSubtype (this=0x7fff3229a640, node=0xe5ad60) at /usr/src/debug/kdepim-4.6.95/messageviewer/objecttreeparser.cpp:1424
#28 0x00007f263d729636 in MessageViewer::ObjectTreeParser::parseObjectTreeInternal (this=0x7fff3229a640, node=0xe5ad60) at /usr/src/debug/kdepim-4.6.95/messageviewer/objecttreeparser.cpp:335
#29 0x00007f263d75d9b1 in MessageViewer::ViewerPrivate::parseContent (this=0xa5a460, content=0xe5ad60) at /usr/src/debug/kdepim-4.6.95/messageviewer/viewer_p.cpp:839
#30 0x00007f263d76062f in MessageViewer::ViewerPrivate::displayMessage (this=0xa5a460) at /usr/src/debug/kdepim-4.6.95/messageviewer/viewer_p.cpp:711
#31 0x00007f263d760d4a in MessageViewer::ViewerPrivate::updateReaderWin (this=0xa5a460) at /usr/src/debug/kdepim-4.6.95/messageviewer/viewer_p.cpp:1920
#32 0x00007f263d763ead in MessageViewer::ViewerPrivate::qt_metacall (this=0xa5a460, _c=QMetaObject::InvokeMetaMethod, _id=27, _a=0x7fff3229ab50) at /usr/src/debug/kdepim-4.6.95/build/messageviewer/viewer_p.moc:220
#33 0x00007f2645bfda5f in QMetaObject::activate (sender=0xa5a4e8, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x0) at kernel/qobject.cpp:3278
#34 0x00007f2645bfd0a9 in QObject::event (this=0xa5a4e8, e=<value optimized out>) at kernel/qobject.cpp:1181
#35 0x00007f2644fb1144 in QApplicationPrivate::notify_helper (this=0x658450, receiver=0xa5a4e8, e=0x7fff3229b2f0) at kernel/qapplication.cpp:4462
#36 0x00007f2644fb96fa in QApplication::notify (this=<value optimized out>, receiver=0xa5a4e8, e=0x7fff3229b2f0) at kernel/qapplication.cpp:4341
#37 0x00007f2646c7c656 in KApplication::notify (this=0x7fff3229b740, receiver=0xa5a4e8, event=0x7fff3229b2f0) at /usr/src/debug/kdelibs-4.6.95/kdeui/kernel/kapplication.cpp:311
#38 0x00007f2645be947c in QCoreApplication::notifyInternal (this=0x7fff3229b740, receiver=0xa5a4e8, event=0x7fff3229b2f0) at kernel/qcoreapplication.cpp:731
#39 0x00007f2645c16df8 in sendEvent (this=0x65c0d0) at kernel/qcoreapplication.h:215
#40 QTimerInfoList::activateTimers (this=0x65c0d0) at kernel/qeventdispatcher_unix.cpp:619
#41 0x00007f2645c13b54 in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:184
#42 0x00007f263c6fbbd3 in g_main_dispatch (context=0x65ba50) at gmain.c:2440
#43 g_main_context_dispatch (context=0x65ba50) at gmain.c:3013
#44 0x00007f263c6fc3b0 in g_main_context_iterate (context=0x65ba50, block=1, dispatch=1, self=<value optimized out>) at gmain.c:3091
#45 0x00007f263c6fc650 in g_main_context_iteration (context=0x65ba50, may_block=1) at gmain.c:3154
#46 0x00007f2645c1422f in QEventDispatcherGlib::processEvents (this=0x6117e0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:422
#47 0x00007f2645056bae in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#48 0x00007f2645be88d2 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#49 0x00007f2645be8ae5 in QEventLoop::exec (this=0x7fff3229b600, flags=...) at kernel/qeventloop.cpp:201
#50 0x00007f2645becf2b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1008
#51 0x000000000040316e in main (argc=<value optimized out>, argv=<value optimized out>) at /usr/src/debug/kdepim-4.6.95/kmail/main.cpp:145

Reported using DrKonqi
Comment 1 Christophe Marin 2011-08-02 20:37:42 UTC
*** Bug 278944 has been marked as a duplicate of this bug. ***
Comment 2 Christophe Marin 2011-12-17 10:59:55 UTC
*** Bug 289128 has been marked as a duplicate of this bug. ***
Comment 3 Christophe Marin 2012-05-03 09:13:41 UTC
*** Bug 291293 has been marked as a duplicate of this bug. ***
Comment 4 Christophe Marin 2012-05-09 13:53:47 UTC
*** Bug 299355 has been marked as a duplicate of this bug. ***
Comment 5 Sergey V Turchin 2012-05-10 11:07:34 UTC
Don't crash if nepomuk switched off
Comment 6 Marc Schiffbauer 2012-05-14 22:24:54 UTC
Confirmed. Disabling nepomuk in systemsettings and killing all nepomuk* processes make me able to use kmail again (current 4.8 branch).

Thanks for the hint!
Comment 7 Laurent Montel 2012-05-15 06:15:56 UTC
?????? do you see this bactrace ???? do you see nepomuk here ????

Please report on good bug report, and not just read "it's crash" ok it's same for me it's crash.

So no nepomuk is not related to this crash.
Comment 8 Sergey V Turchin 2012-05-15 10:47:27 UTC
No nepomuk in backtrace. Backtrace same as in description.
Comment 9 Sergey V Turchin 2012-05-15 10:49:51 UTC
When turn nepomuk on #299357 appear too.
Comment 10 Marc Schiffbauer 2012-05-15 18:24:51 UTC
(In reply to comment #7)
> ?????? do you see this bactrace ???? do you see nepomuk here ????
> 
> Please report on good bug report, and not just read "it's crash" ok it's
> same for me it's crash.
> 
> So no nepomuk is not related to this crash.

Hi Laurent,

Its true that there is nothing about nepomuk in the BT. But it is also true, that this crash only occurs if nepomuk is enabled.
BTW: Enabling nepomuk also make akonadi nepomuk feeder and akonadi mail agent crash immediately. Are you interested in those
BTs as well?

Thanks
-Marc
Comment 11 Laurent Montel 2012-05-15 21:29:24 UTC
(In reply to comment #10)
> (In reply to comment #7)
> > ?????? do you see this bactrace ???? do you see nepomuk here ????
> > 
> > Please report on good bug report, and not just read "it's crash" ok it's
> > same for me it's crash.
> > 
> > So no nepomuk is not related to this crash.
> 
> Hi Laurent,
> 
> Its true that there is nothing about nepomuk in the BT. But it is also true,
> that this crash only occurs if nepomuk is enabled.
> BTW: Enabling nepomuk also make akonadi nepomuk feeder and akonadi mail
> agent crash immediately. Are you interested in those
> BTs as well?
> 
> Thanks
> -Marc

Yes please put bt
Thanks
Comment 12 Sergey V Turchin 2012-05-16 10:31:49 UTC
(In reply to comment #11)
> please put bt
http://bugs.kde.org/299357
Comment 13 Christophe Marin 2012-05-17 21:22:23 UTC
*** Bug 300203 has been marked as a duplicate of this bug. ***
Comment 14 Marc Schiffbauer 2012-05-19 23:40:42 UTC
> Yes please put bt
> Thanks

I only can reproduce the nepomuk feeder crash atm. (Bug 299357)

Steps to reproduce:

1. akonadictl stop (wait until 'akonadictl status' tells that its stopped)
2. enable nepomuk
3. akonadictl start -> crash
Comment 15 Sergey V Turchin 2012-05-23 15:08:37 UTC
No problem after building soprano and strigi with clucene-core-2.3.3.4 (was clucene-0.9.21)
Comment 16 Sergey V Turchin 2012-05-23 15:43:46 UTC
But only with mail indexing. When turn file indexing on, problem occur again.
Comment 17 Sergey V Turchin 2012-05-30 11:26:06 UTC
Reverting kdelibs/nepomuk/* code to v4.8.3 tag fixes the problem
Comment 18 Rex Dieter 2012-06-08 12:47:26 UTC
Created attachment 71664 [details]
New crash information added by DrKonqi

kmail (4.8.4) on KDE Platform 4.8.4 (4.8.4) using Qt 4.8.2

- What I was doing when the application crashed:

attempt to refresh my gmail imap inbox using kmail from kdepim-4.8.4

-- Backtrace (Reduced):
#7  ~KSharedPtr (this=0xcb7050, __in_chrg=<optimized out>) at /usr/src/debug/kdelibs-4.8.4/kdecore/util/ksharedptr.h:90
#8  ~ParsingData (this=0xcb7050, __in_chrg=<optimized out>) at /usr/src/debug/kdelibs-4.8.4/kdecore/services/ktraderparse.cpp:40
#9  qThreadStorage_deleteData<KTraderParse::ParsingData> (d=0xcb7050) at /usr/include/QtCore/qthreadstorage.h:97
#10 QThreadStorage<KTraderParse::ParsingData*>::deleteData (x=0xcb7050) at /usr/include/QtCore/qthreadstorage.h:140
#11 0x00000039874793e0 in QThreadStorageData::set (this=<optimized out>, p=0x19bef40) at thread/qthreadstorage.cpp:165
Comment 19 Rex Dieter 2012-06-08 12:58:11 UTC
confirmed that disabling nepomuk completely and crash no longer occurs.  Seems to still happen even if I disable either (or both) of Nepomuk File Indexer, Email Indexer
Comment 20 Rex Dieter 2012-06-08 13:06:05 UTC
updating summary to match findings of last 2 folks (including me)
Comment 21 Sergey V Turchin 2012-06-08 13:30:26 UTC
Don't crash with lastest 4.8 branch, but akonadi_nepomuk_feeder still "System busy, indexing suspended"
Comment 22 François 2012-06-08 20:20:09 UTC
Created attachment 71675 [details]
New crash information added by DrKonqi

kmail (4.8.4) on KDE Platform 4.8.4 (4.8.4) using Qt 4.8.2

- What I was doing when the application crashed:
crash by selecting an incoming email after boot

- Custom settings of the application:
2 imap account and 2 pop
4 smtp account

default configuration

-- Backtrace (Reduced):
#6  0x00007feedfeda470 in QThreadStorageData::set(void*) () from /usr/lib/libQtCore.so.4
[...]
#8  0x00007feee17846f2 in KServiceTypeTrader::applyConstraints(QList<KSharedPtr<KService> >&, QString const&) () from /usr/lib/libkdecore.so.5
#9  0x00007feee178487c in KServiceTypeTrader::defaultOffers(QString const&, QString const&) const () from /usr/lib/libkdecore.so.5
#10 0x00007feee1784c31 in KServiceTypeTrader::query(QString const&, QString const&) const () from /usr/lib/libkdecore.so.5
[...]
#12 0x00007feed1920a3a in KEmoticons::KEmoticons() () from /usr/lib/libkemoticons.so.4
Comment 23 François 2012-06-08 20:24:09 UTC
have try without nepomuk, but crash again
Comment 24 Franz Trischberger 2012-06-09 12:37:34 UTC
I can confirm that turning off nepomuk stops kmail from crashing.
kontact does not crash when nepomuk is turned on and kmail gets loaded, therefor it does not stop correctly - it keeps running and prevents starting a new instance.

Here is the backtrace of the locked up instance:

(gdb) bt
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:39
#1  0x00007f507b24771b in _q_futex (val2=0, addr2=0x0, timeout=0x0, val=2, op=0, addr=0x27fe930) at thread/qmutex_unix.cpp:99
#2  QMutexPrivate::wait (this=0x27fe930, timeout=<optimized out>) at thread/qmutex_unix.cpp:113
#3  0x00007f507b2434fd in QMutex::lockInternal (this=<optimized out>) at thread/qmutex.cpp:450
#4  0x00007f506e339c5a in lockInline (this=0x27fe5e8) at /usr/include/qt4/QtCore/qmutex.h:198
#5  QMutexLocker (m=0x27fe5e8, this=<synthetic pointer>) at /usr/include/qt4/QtCore/qmutex.h:109
#6  Soprano::Client::SocketHandler::~SocketHandler (this=0x2800a90, __in_chrg=<optimized out>) at /var/tmp/paludis/dev-libs-soprano-2.7.6/work/soprano-2.7.6/client/clientconnection.cpp:58
#7  0x00007f506e339d29 in Soprano::Client::SocketHandler::~SocketHandler (this=0x2800a90, __in_chrg=<optimized out>) at /var/tmp/paludis/dev-libs-soprano-2.7.6/work/soprano-2.7.6/client/clientconnection.cpp:61
#8  0x00007f507b246c0c in QThreadStorageData::set (this=0x2436230, p=0x27ff7e0) at thread/qthreadstorage.cpp:165
#9  0x00007f506e33774f in qThreadStorage_setLocalData<Soprano::Client::SocketHandler> (d=..., t=<optimized out>) at /usr/include/qt4/QtCore/qthreadstorage.h:92
#10 setLocalData (t=0x27ff7e0, this=<optimized out>) at /usr/include/qt4/QtCore/qthreadstorage.h:155
#11 Soprano::Client::ClientConnection::socketForCurrentThread (this=0x2511020) at /var/tmp/paludis/dev-libs-soprano-2.7.6/work/soprano-2.7.6/client/clientconnection.cpp:95
#12 0x00007f506e3377b9 in Soprano::Client::ClientConnection::connectInCurrentThread (this=<optimized out>) at /var/tmp/paludis/dev-libs-soprano-2.7.6/work/soprano-2.7.6/client/clientconnection.cpp:800
#13 0x00007f506e336d8a in Soprano::Client::LocalSocketClient::connect (this=0x27fda78, name="/tmp/ksocket-franz/nepomuk-socket") at /var/tmp/paludis/dev-libs-soprano-2.7.6/work/soprano-2.7.6/client/localsocketclient.cpp:141
#14 0x00007f50728a1157 in init (forced=true, this=0x27fda50) at /var/tmp/paludis/kde-base-kdelibs-4.8.4/work/kdelibs-4.8.4/nepomuk/core/nepomukmainmodel.cpp:103
#15 Nepomuk::MainModel::init (this=0x27fd380) at /var/tmp/paludis/kde-base-kdelibs-4.8.4/work/kdelibs-4.8.4/nepomuk/core/nepomukmainmodel.cpp:177
#16 0x00007f5072899f20 in Nepomuk::ResourceManager::init (this=0x27fcc20) at /var/tmp/paludis/kde-base-kdelibs-4.8.4/work/kdelibs-4.8.4/nepomuk/core/resourcemanager.cpp:323
#17 0x00007f507289a105 in Nepomuk::ResourceManager::ResourceManager (this=0x27fcc20) at /var/tmp/paludis/kde-base-kdelibs-4.8.4/work/kdelibs-4.8.4/nepomuk/core/resourcemanager.cpp:286
#18 0x00007f507289a155 in Nepomuk::ResourceManager::instance () at /var/tmp/paludis/kde-base-kdelibs-4.8.4/work/kdelibs-4.8.4/nepomuk/core/resourcemanager.cpp:311
#19 0x00007f50728b0283 in Nepomuk::ResourceWatcher::stop (this=0x28061b0) at /var/tmp/paludis/kde-base-kdelibs-4.8.4/work/kdelibs-4.8.4/nepomuk/core/resourcewatcher.cpp:140
#20 0x00007f50728b02e0 in Nepomuk::ResourceWatcher::~ResourceWatcher (this=0x28061b0, __in_chrg=<optimized out>) at /var/tmp/paludis/kde-base-kdelibs-4.8.4/work/kdelibs-4.8.4/nepomuk/core/resourcewatcher.cpp:79
#21 0x00007f50728b0339 in Nepomuk::ResourceWatcher::~ResourceWatcher (this=0x28061b0, __in_chrg=<optimized out>) at /var/tmp/paludis/kde-base-kdelibs-4.8.4/work/kdelibs-4.8.4/nepomuk/core/resourcewatcher.cpp:81
#22 0x00007f507b3571e1 in QObjectPrivate::deleteChildren (this=0x27fc8f0) at kernel/qobject.cpp:1908
#23 0x00007f507b35d20c in QObject::~QObject (this=0x27f9530, __in_chrg=<optimized out>) at kernel/qobject.cpp:927
#24 0x00007f507289d4f9 in Nepomuk::ResourceManager::~ResourceManager (this=0x27f9530, __in_chrg=<optimized out>) at /var/tmp/paludis/kde-base-kdelibs-4.8.4/work/kdelibs-4.8.4/nepomuk/core/resourcemanager.cpp:299
#25 0x00007f507b3571e1 in QObjectPrivate::deleteChildren (this=0x1f98da0) at kernel/qobject.cpp:1908
#26 0x00007f507b35d20c in QObject::~QObject (this=0x7fff16024130, __in_chrg=<optimized out>) at kernel/qobject.cpp:927
#27 0x00007f507a6fa7f7 in QApplication::~QApplication (this=0x7fff16024130, __in_chrg=<optimized out>) at kernel/qapplication.cpp:1095
#28 0x0000000000403bff in main (argc=1, argv=0x7fff16024758) at /var/tmp/paludis/kde-base-kontact-4.8.4/work/kontact-4.8.4/kontact/src/main.cpp:221

It hangs in a locked mutex.
Comment 25 François 2012-06-09 14:45:10 UTC
nepomuk was not correctly stopped (my mistake), kmail works effectively if we deactivate it
thank you
Comment 26 Franz Trischberger 2012-06-10 10:53:36 UTC
kmail is not the only affected application:
https://bugs.kde.org/show_bug.cgi?id=301453
Solution: Update to soprano-2.7.56 (current beta1 :/)
Comment 27 Jekyll Wu 2012-06-10 23:05:59 UTC
*** Bug 301602 has been marked as a duplicate of this bug. ***
Comment 28 K Woelfel 2012-06-12 11:37:30 UTC
Created attachment 71757 [details]
New crash information added by DrKonqi

kmail (4.8.4) on KDE Platform 4.8.4 (4.8.4) "release 511" using Qt 4.8.2

- What I was doing when the application crashed:
I opened kmail and selected one email for reading

- Custom settings of the application:
Other than the original bug description, it also happens for me if, I don't set the message pane next to the message list. It happens as soon as I doubleclick a message for reading.

-- Backtrace (Reduced):
#7  ~KSharedPtr (this=0xf85130, __in_chrg=<optimized out>) at /usr/src/debug/kdelibs-4.8.4/kdecore/util/ksharedptr.h:90
#8  ~ParsingData (this=0xf85130, __in_chrg=<optimized out>) at /usr/src/debug/kdelibs-4.8.4/kdecore/services/ktraderparse.cpp:40
#9  qThreadStorage_deleteData<KTraderParse::ParsingData> (d=0xf85130) at /usr/include/QtCore/qthreadstorage.h:97
#10 QThreadStorage<KTraderParse::ParsingData*>::deleteData (x=0xf85130) at /usr/include/QtCore/qthreadstorage.h:140
#11 0x00007f152b6115ed in QThreadStorageData::set (this=0x1557690, p=0x1a645d0) at thread/qthreadstorage.cpp:165
Comment 29 K Woelfel 2012-06-12 12:03:28 UTC
Created attachment 71758 [details]
New crash information added by DrKonqi

kmail (4.8.4) on KDE Platform 4.8.4 (4.8.4) "release 511" using Qt 4.8.2

Finally, my here prvious reported crash seems not to be related to nepomuk, because I deactivated nepomuk and the same crash happend again.

-- Backtrace (Reduced):
#6  fullLookupForWriting<char const*, WTF::HashSetTranslatorAdapter<WTF::StringImpl*, WTF::HashTraits<WTF::StringImpl*>, char const*, WTF::CStringTranslator> > (key=<synthetic pointer>, this=0x7f67b89b9e10) at ../../../Source/JavaScriptCore/wtf/text/AtomicString.cpp:368
#7  addPassingHashCode<char const*, char const*, WTF::HashSetTranslatorAdapter<WTF::StringImpl*, WTF::HashTraits<WTF::StringImpl*>, char const*, WTF::CStringTranslator> > (this=0x7f67b89b9e10, extra=<synthetic pointer>, key=<synthetic pointer>) at ../../../Source/JavaScriptCore/wtf/HashTable.h:726
#8  add<char const*, WTF::CStringTranslator> (this=<optimized out>, value=<synthetic pointer>) at ../../../Source/JavaScriptCore/wtf/HashSet.h:189
#9  addToStringTable<char const*, WTF::CStringTranslator> (value=<synthetic pointer>) at ../../../Source/JavaScriptCore/wtf/text/AtomicString.cpp:80
#10 WTF::AtomicString::add (c=0x7f67bb89a020 "#text") at ../../../Source/JavaScriptCore/wtf/text/AtomicString.cpp:130
Comment 30 David Faure 2012-06-14 10:03:39 UTC
My theory would be that nepomuk corrups memory in QThreadStorage stuff, which then makes KTraderParse crash (it uses its own QThreadStorage, but maybe Qt puts these close to each other in memory). A bit far-fetched though, only a valgrind log would tell.

In other news, there have been fixes in nepomuk very recently, to fix crashes with older versions of soprano, so maybe it fixes this.
http://commits.kde.org/kdelibs/bde5aad1e9f7bfb6f8d5c60197797de4a315158d
http://commits.kde.org/kdelibs/76e0376d7582cfe5b898c56bf3779ca2279dace8
Comment 31 K Woelfel 2012-06-14 10:10:07 UTC
(In reply to comment #29)

Sorry, my previous comment was wrong. After disabling nepomuk, I did not kill remaining nepomuk related processes, that was why the crash still happened. When I disable nepomuk and reboot, than the crash does definitely not happen anymore.

I would also like to not that the crash happened after updating from 4.8.3 to 4.8.4 on OpenSuSe.

> Created attachment 71758 [details]
> New crash information added by DrKonqi
> 
> kmail (4.8.4) on KDE Platform 4.8.4 (4.8.4) "release 511" using Qt 4.8.2
> 
> Finally, my here prvious reported crash seems not to be related to nepomuk,
> because I deactivated nepomuk and the same crash happend again.
> 
> -- Backtrace (Reduced):
> #6  fullLookupForWriting<char const*,
> WTF::HashSetTranslatorAdapter<WTF::StringImpl*,
> WTF::HashTraits<WTF::StringImpl*>, char const*, WTF::CStringTranslator> >
> (key=<synthetic pointer>, this=0x7f67b89b9e10) at
> ../../../Source/JavaScriptCore/wtf/text/AtomicString.cpp:368
> #7  addPassingHashCode<char const*, char const*,
> WTF::HashSetTranslatorAdapter<WTF::StringImpl*,
> WTF::HashTraits<WTF::StringImpl*>, char const*, WTF::CStringTranslator> >
> (this=0x7f67b89b9e10, extra=<synthetic pointer>, key=<synthetic pointer>) at
> ../../../Source/JavaScriptCore/wtf/HashTable.h:726
> #8  add<char const*, WTF::CStringTranslator> (this=<optimized out>,
> value=<synthetic pointer>) at
> ../../../Source/JavaScriptCore/wtf/HashSet.h:189
> #9  addToStringTable<char const*, WTF::CStringTranslator> (value=<synthetic
> pointer>) at ../../../Source/JavaScriptCore/wtf/text/AtomicString.cpp:80
> #10 WTF::AtomicString::add (c=0x7f67bb89a020 "#text") at
> ../../../Source/JavaScriptCore/wtf/text/AtomicString.cpp:130
Comment 32 David Faure 2012-06-14 13:26:50 UTC
See https://bugs.kde.org/show_bug.cgi?id=301453 for more information.
Comment 33 Robert Riemann 2012-06-17 22:28:52 UTC
Deactivating Nepomuk also "solved" my KMail-Crashing problems.
Comment 34 Myriam Schweingruber 2012-08-18 21:38:59 UTC
Closing based on comment #32