Bug 325467

Summary:	KMail random crashes (scavengerThread)
Product:	[Applications] kmail2	Reporter:	Oleg <prcoder>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	crash	CC:	prcoder
Priority:	NOR	Keywords:	drkonqi
Version:	4.11.1
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi

Description Oleg 2013-09-30 16:53:27 UTC

Application: kmail (4.11.1)
KDE Platform Version: 4.11.1
Qt Version: 4.8.5
Operating System: Linux 3.11.1-300.fc20.i686+PAE i686
Distribution: "Fedora release 20 (Heisenbug)"

-- Information about the crash:
KMail random crashes, often at attempt to exit. May be due to nvidia-304xx/libGL.so.1

The crash can be reproduced sometimes.

-- Backtrace:
Application: KMail (kmail), signal: Aborted
Using host libthread_db library "/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0xb7744800 (LWP 1739))]

Thread 5 (Thread 0xb483cb40 (LWP 1745)):
#0  0xb77ac424 in __kernel_vsyscall ()
#1  0x47feb7ac in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i486/pthread_cond_wait.S:187
#2  0x45ee2c64 in WTF::TCMalloc_PageHeap::scavengerThread (this=this@entry=0x466bbbe0 <WTF::pageheap_memory>) at /usr/src/debug/webkit-qtwebkit-23/Source/WTF/wtf/FastMalloc.cpp:2571
#3  0x45ee2cb0 in WTF::TCMalloc_PageHeap::runScavengerThread (context=0x466bbbe0 <WTF::pageheap_memory>) at /usr/src/debug/webkit-qtwebkit-23/Source/WTF/wtf/FastMalloc.cpp:1767
#4  0x48cbef41 in ?? () from /usr/lib/nvidia-304xx/libGL.so.1
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Thread 4 (Thread 0xb3ea3b40 (LWP 1746)):
#0  0xb77ac424 in __kernel_vsyscall ()
#1  0x47feb7ac in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i486/pthread_cond_wait.S:187
#2  0x45f132a4 in WTF::ThreadCondition::wait (this=this@entry=0xb3f8a7dc, mutex=...) at /usr/src/debug/webkit-qtwebkit-23/Source/WTF/wtf/ThreadingPthreads.cpp:379
#3  0x45be253c in JSC::BlockAllocator::blockFreeingThreadMain (this=0xb3f8a750) at /usr/src/debug/webkit-qtwebkit-23/Source/JavaScriptCore/heap/BlockAllocator.cpp:128
#4  0x45ef8ef9 in WTF::threadEntryPoint (contextData=0xb3f3dbe0) at /usr/src/debug/webkit-qtwebkit-23/Source/WTF/wtf/Threading.cpp:69
#5  0x45f12baa in WTF::wtfThreadEntryPoint (param=0x97ee2a8) at /usr/src/debug/webkit-qtwebkit-23/Source/WTF/wtf/ThreadingPthreads.cpp:196
#6  0x48cbef41 in ?? () from /usr/lib/nvidia-304xx/libGL.so.1
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Thread 3 (Thread 0xb3055b40 (LWP 1747)):
#0  0xb77ac424 in __kernel_vsyscall ()
#1  0x47eb668b in read () at ../sysdeps/unix/syscall-template.S:81
#2  0x48cbbc7b in ?? () from /usr/lib/nvidia-304xx/libGL.so.1
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Thread 2 (Thread 0x693eb40 (LWP 16178)):
#0  0xb77ac424 in __kernel_vsyscall ()
#1  0x47ed6dd2 in __GI___clock_gettime (clock_id=1, tp=0x693de94) at ../sysdeps/unix/clock_gettime.c:115
#2  0x4b4195dd in do_gettime (frac=0x693de88, sec=0x693de80) at tools/qelapsedtimer_unix.cpp:127
#3  qt_gettime () at tools/qelapsedtimer_unix.cpp:144
#4  0x4b509013 in updateCurrentTime (this=0x60019bc) at kernel/qeventdispatcher_unix.cpp:354
#5  QTimerInfoList::timerWait (this=0x60019bc, tm=...) at kernel/qeventdispatcher_unix.cpp:460
#6  0x4b50742b in timerSourcePrepareHelper (src=<optimized out>, timeout=0x693df88) at kernel/qeventdispatcher_glib.cpp:136
#7  0x4b5074dd in timerSourcePrepare (source=0x6001988, timeout=timeout@entry=0x693df88) at kernel/qeventdispatcher_glib.cpp:169
#8  0x4b9cedaf in g_main_context_prepare (context=<optimized out>, context@entry=0x6000500, priority=priority@entry=0x693dfe4) at gmain.c:3339
#9  0x4b9cf777 in g_main_context_iterate (context=context@entry=0x6000500, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3692
#10 0x4b9cf9d9 in g_main_context_iteration (context=0x6000500, may_block=1) at gmain.c:3773
#11 0x4b50762f in QEventDispatcherGlib::processEvents (this=0x6000488, flags=...) at kernel/qeventdispatcher_glib.cpp:427
#12 0x4b4d43b0 in QEventLoop::processEvents (this=this@entry=0x693e0f4, flags=...) at kernel/qeventloop.cpp:149
#13 0x4b4d4741 in QEventLoop::exec (this=this@entry=0x693e0f4, flags=...) at kernel/qeventloop.cpp:204
#14 0x4b3b7d55 in QThread::exec (this=this@entry=0xa452668) at thread/qthread.cpp:536
#15 0x4b4b31e1 in QInotifyFileSystemWatcherEngine::run (this=0xa452668) at io/qfilesystemwatcher_inotify.cpp:256
#16 0x4b3ba81b in QThreadPrivate::start (arg=0xa452668) at thread/qthread_unix.cpp:338
#17 0x48cbef41 in ?? () from /usr/lib/nvidia-304xx/libGL.so.1
#18 0x5c8b0824 in ?? ()
#19 0x456e6f73 in WebCore::jsDOMSettableTokenListValue () from /lib/libQtWebKit.so.4
#20 0x00004b76 in ?? ()
#21 0x00000000 in ?? ()

Thread 1 (Thread 0xb7744800 (LWP 1739)):
[KCrash Handler]
#7  0xb77ac424 in __kernel_vsyscall ()
#8  0x47dffba6 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#9  0x47e013e3 in __GI_abort () at abort.c:89
#10 0x48085a3f in __gnu_cxx::__verbose_terminate_handler () at ../../../../libstdc++-v3/libsupc++/vterminate.cc:50
#11 0x480834f4 in __cxxabiv1::__terminate (handler=0x48085910 <__gnu_cxx::__verbose_terminate_handler()>) at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:38
#12 0x48082386 in __cxa_call_terminate (ue_header=0xbff06b40) at ../../../../libstdc++-v3/libsupc++/eh_call.cc:54
#13 0x48082ff5 in __cxxabiv1::__gxx_personality_v0 (version=1, actions=6, exception_class=5138137972254386944, ue_header=0xbff06b40, context=0xbfe33dd0) at ../../../../libstdc++-v3/libsupc++/eh_personality.cc:670
#14 0x4802c06c in _Unwind_RaiseException_Phase2 (exc=exc@entry=0xbff06b40, context=context@entry=0xbfe33dd0) at ../../../libgcc/unwind.inc:62
#15 0x4802c5ce in _Unwind_Resume (exc=exc@entry=0xbff06b40) at ../../../libgcc/unwind.inc:230
#16 0x4fcf88d4 in ~QForeachContainer (this=0xbfe33eac, __in_chrg=<optimized out>) at /usr/include/QtCore/qglobal.h:2365
#17 KMKernel::dumpDeadLetters (this=0xbfe34b68) at /usr/src/debug/kdepim-4.11.1/kmail/kmkernel.cpp:1381
#18 0x4fcfa121 in kmCrashHandler (sigId=6) at /usr/src/debug/kdepim-4.11.1/kmail/kmkernel.cpp:1216
#19 0x4c467827 in KCrash::defaultCrashHandler (sig=6) at /usr/src/debug/kdelibs-4.11.1/kdeui/util/kcrash.cpp:307
#20 <signal handler called>
#21 0xb77ac424 in __kernel_vsyscall ()
#22 0x47dffba6 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#23 0x47e013e3 in __GI_abort () at abort.c:89
#24 0x48085ab5 in __gnu_cxx::__verbose_terminate_handler () at ../../../../libstdc++-v3/libsupc++/vterminate.cc:95
#25 0x480834f4 in __cxxabiv1::__terminate (handler=0x48085910 <__gnu_cxx::__verbose_terminate_handler()>) at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:38
#26 0x48083530 in std::terminate () at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:48
#27 0x480837fb in __cxxabiv1::__cxa_rethrow () at ../../../../libstdc++-v3/libsupc++/eh_throw.cc:122
#28 0x4b4d493d in QEventLoop::exec (this=this@entry=0xbfe34a04, flags=...) at kernel/qeventloop.cpp:218
#29 0x4b4da3fb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1221
#30 0x41153365 in QApplication::exec () at kernel/qapplication.cpp:3823
#31 0x0804a63c in main (argc=3, argv=0xbfe34ca4) at /usr/src/debug/kdepim-4.11.1/kmail/main.cpp:146

Possible duplicates by query: bug 323692, bug 323586, bug 308801, bug 306218, bug 305584.

Reported using DrKonqi

Comment 1 Oleg 2013-10-02 16:39:09 UTC

Created attachment 82614 [details]
New crash information added by DrKonqi

kmail (4.11.2) on KDE Platform 4.11.2 using Qt 4.8.5

Kmail randomly crashes when Idle or checking IMAP folders

-- Backtrace (Reduced):
#8  0x47dffba6 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#9  0x47e013e3 in __GI_abort () at abort.c:89
#10 0x48085ab5 in __gnu_cxx::__verbose_terminate_handler () at ../../../../libstdc++-v3/libsupc++/vterminate.cc:95
#11 0x480834f4 in __cxxabiv1::__terminate (handler=0x48085910 <__gnu_cxx::__verbose_terminate_handler()>) at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:38
#12 0x48083530 in std::terminate () at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:48

Comment 2 Jekyll Wu 2013-10-04 20:53:31 UTC

*** Bug 325634 has been marked as a duplicate of this bug. ***

Comment 3 Oleg 2013-10-09 16:35:15 UTC

Created attachment 82754 [details]
New crash information added by DrKonqi

kmail (4.11.2) on KDE Platform 4.11.2 using Qt 4.8.5

KMail crushes and hungup while exiting

-- Backtrace (Reduced):
#8  0x48be4ba6 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#9  0x48be63e3 in __GI_abort () at abort.c:89
#10 0x48e6aab5 in __gnu_cxx::__verbose_terminate_handler () at ../../../../libstdc++-v3/libsupc++/vterminate.cc:95
#11 0x48e684f4 in __cxxabiv1::__terminate (handler=0x48e6a910 <__gnu_cxx::__verbose_terminate_handler()>) at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:38
#12 0x48e68530 in std::terminate () at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:48

Comment 4 Oleg 2013-10-10 18:00:53 UTC

Created attachment 82770 [details]
New crash information added by DrKonqi

kmail (4.11.2) on KDE Platform 4.11.2 using Qt 4.8.5

Kmail periodically crshes in scavengerThread

-- Backtrace (Reduced):
#8  0x48be4ba6 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#9  0x48be63e3 in __GI_abort () at abort.c:89
#10 0x48e6aab5 in __gnu_cxx::__verbose_terminate_handler () at ../../../../libstdc++-v3/libsupc++/vterminate.cc:95
#11 0x48e684f4 in __cxxabiv1::__terminate (handler=0x48e6a910 <__gnu_cxx::__verbose_terminate_handler()>) at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:38
#12 0x48e68530 in std::terminate () at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:48

Comment 5 Denis Kurz 2016-09-24 18:23:10 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 kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.

Comment 6 Denis Kurz 2017-01-07 22:16:56 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.