Bug 302226 - Kmail crashed on close
Summary: Kmail crashed on close
Status: RESOLVED DUPLICATE of bug 302452
Alias: None
Product: nepomuk
Classification: Miscellaneous
Component: general (show other bugs)
Version: 4.8
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Sebastian Trueg
URL:
Keywords:
: 303599 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-06-20 10:12 UTC by S. Burmeister
Modified: 2012-08-08 15:00 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (2.20 KB, text/plain)
2012-06-24 18:09 UTC, S. Burmeister
Details

Note You need to log in before you can comment on or make changes to this bug.
Description S. Burmeister 2012-06-20 10:12:10 UTC
Application: kmail (4.8.4)
KDE Platform Version: 4.8.4 (4.8.4) "release 513"
Qt Version: 4.8.2
Operating System: Linux 3.1.10-1.9-desktop x86_64
Distribution: "openSUSE 12.1 (x86_64)"

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

After I clicked on the close icon in kmail's title-bar it crashed.

-- Backtrace:
Application: KMail (kmail), signal: Aborted
[Current thread is 1 (Thread 0x7f895dd9f780 (LWP 7225))]

Thread 3 (Thread 0x7f893f81e700 (LWP 7543)):
#0  0x00007f8958ed9e6c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007f894f573c12 in ?? () from /usr/lib64/libQtWebKit.so.4
#2  0x00007f894f573c49 in ?? () from /usr/lib64/libQtWebKit.so.4
#3  0x00007f8958ed5f05 in start_thread () from /lib64/libpthread.so.0
#4  0x00007f895b0d110d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f893d402700 (LWP 24774)):
#0  0x00007f8958eda1eb in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007f895c602a8f in wait (time=30000, this=0x1340140) at thread/qwaitcondition_unix.cpp:84
#2  QWaitCondition::wait (this=<optimized out>, mutex=0x13403c8, time=30000) at thread/qwaitcondition_unix.cpp:158
#3  0x00007f895c5f5e9f in QThreadPoolThread::run (this=0x1341810) at concurrent/qthreadpool.cpp:141
#4  0x00007f895c60261b in QThreadPrivate::start (arg=0x1341810) at thread/qthread_unix.cpp:307
#5  0x00007f8958ed5f05 in start_thread () from /lib64/libpthread.so.0
#6  0x00007f895b0d110d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f895dd9f780 (LWP 7225)):
[KCrash Handler]
#6  0x00007f895b02ad95 in raise () from /lib64/libc.so.6
#7  0x00007f895b02c2ab in abort () from /lib64/libc.so.6
#8  0x00007f895b65af2d in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib64/libstdc++.so.6
#9  0x00007f895b6590d6 in ?? () from /usr/lib64/libstdc++.so.6
#10 0x00007f895b659103 in std::terminate() () from /usr/lib64/libstdc++.so.6
#11 0x00007f895b659246 in __cxa_rethrow () from /usr/lib64/libstdc++.so.6
#12 0x00007f895c61e2db in QHashData::detach_helper2 (this=0x7f88f0166580, node_duplicate=0x7f8953e83c10 <QHash<KUrl, QHashDummyValue>::duplicateNode(QHashData::Node*, void*)>, node_delete=0x7f8953e83bb0 <QHash<KUrl, QHashDummyValue>::deleteNode2(QHashData::Node*)>, nodeSize=32, nodeAlign=8) at tools/qhash.cpp:227
#13 0x00007f8953e84782 in QHash<KUrl, QHashDummyValue>::detach_helper (this=0x7ffff7a18630) at /usr/include/QtCore/qhash.h:584
#14 0x00007f8953e7f459 in detach (this=0x7ffff7a18630) at /usr/include/QtCore/qhash.h:303
#15 QHash (other=..., this=0x7ffff7a18630) at /usr/include/QtCore/qhash.h:282
#16 QSet (this=0x7ffff7a18630, other=...) at /usr/include/QtCore/qset.h:60
#17 QForeachContainer (t=..., this=0x7ffff7a18630) at /usr/include/QtCore/qglobal.h:2345
#18 Nepomuk::ResourceData::resetAll (this=0x7f88f0159c70, isDelete=true) at /usr/src/debug/kdelibs-4.8.4/nepomuk/core/resourcedata.cpp:174
#19 0x00007f8953e7ff3e in Nepomuk::ResourceData::~ResourceData (this=0x7f88f0159c70, __in_chrg=<optimized out>) at /usr/src/debug/kdelibs-4.8.4/nepomuk/core/resourcedata.cpp:106
#20 0x00007f8953e87f26 in Nepomuk::ResourceManagerPrivate::cleanupCache (this=<optimized out>, num=-1) at /usr/src/debug/kdelibs-4.8.4/nepomuk/core/resourcemanager.cpp:194
#21 0x00007f8953e8816c in Nepomuk::ResourceManager::~ResourceManager (this=0x8ba580, __in_chrg=<optimized out>) at /usr/src/debug/kdelibs-4.8.4/nepomuk/core/resourcemanager.cpp:292
#22 0x00007f8953e88239 in Nepomuk::ResourceManager::~ResourceManager (this=0x8ba580, __in_chrg=<optimized out>) at /usr/src/debug/kdelibs-4.8.4/nepomuk/core/resourcemanager.cpp:299
#23 0x00007f895c7132f5 in QObjectPrivate::deleteChildren (this=0x664720) at kernel/qobject.cpp:1917
#24 0x00007f895c71955c in QObject::~QObject (this=0x7ffff7a18a80, __in_chrg=<optimized out>) at kernel/qobject.cpp:927
#25 0x00007f895ba8da1e in QApplication::~QApplication (this=0x7ffff7a18a80, __in_chrg=<optimized out>) at kernel/qapplication.cpp:1095
#26 0x0000000000402e27 in ~KMailApplication (this=0x7ffff7a18a80, __in_chrg=<optimized out>) at /usr/src/debug/kdepim-4.8.4/kmail/main.cpp:42
#27 main (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/kdepim-4.8.4/kmail/main.cpp:113

Possible duplicates by query: bug 180214.

Reported using DrKonqi
Comment 1 S. Burmeister 2012-06-24 18:09:52 UTC
Created attachment 72099 [details]
New crash information added by DrKonqi

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

- What I was doing when the application crashed:

Another crash after closing kmail via the windeco button.

-- Backtrace (Reduced):
#8  0x00007f87c2f92f26 in Nepomuk::ResourceManagerPrivate::cleanupCache (this=<optimized out>, num=-1) at /usr/src/debug/kdelibs-4.8.4/nepomuk/core/resourcemanager.cpp:194
#9  0x00007f87c2f9316c in Nepomuk::ResourceManager::~ResourceManager (this=0x66e870, __in_chrg=<optimized out>) at /usr/src/debug/kdelibs-4.8.4/nepomuk/core/resourcemanager.cpp:292
#10 0x00007f87c2f93239 in Nepomuk::ResourceManager::~ResourceManager (this=0x66e870, __in_chrg=<optimized out>) at /usr/src/debug/kdelibs-4.8.4/nepomuk/core/resourcemanager.cpp:299
#11 0x00007f87cb81e2f5 in QObjectPrivate::deleteChildren (this=0x660bd0) at kernel/qobject.cpp:1917
#12 0x00007f87cb82455c in QObject::~QObject (this=0x7fffbb1a6660, __in_chrg=<optimized out>) at kernel/qobject.cpp:927
Comment 2 Jekyll Wu 2012-07-16 17:14:14 UTC
*** Bug 303599 has been marked as a duplicate of this bug. ***
Comment 3 Vishesh Handa 2012-08-08 15:00:45 UTC

*** This bug has been marked as a duplicate of bug 302452 ***