Bug 280225

Summary:	Crash on startup
Product:	[Applications] kontact	Reporter:	Torben Jensby Christensen <tjc>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	tjc
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	New crash information added by DrKonqi

Description Torben Jensby Christensen 2011-08-16 21:36:20 UTC

Application: kontact (4.7.0)
KDE Platform Version: 4.7.00 (4.7.0) "release 10"
Qt Version: 4.7.3
Operating System: Linux 2.6.37.6-0.7-desktop x86_64
Distribution: "openSUSE 11.4 (x86_64)"

-- Information about the crash:
Each start of kontact is very slow, and when the startup processes have finished it crashes

-- Backtrace:
Application: Kontact (kontact), signal: Aborted
[Current thread is 1 (Thread 0x7ffc0f8a7760 (LWP 7633))]

Thread 2 (Thread 0x7ffbf2e9f700 (LWP 7636)):
#0  0x00007ffc07c4438c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007ffc0c2c31d4 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/libQtWebKit.so.4
#2  0x00007ffc07c3fa3f in start_thread () from /lib64/libpthread.so.0
#3  0x00007ffc0ce6567d in clone () from /lib64/libc.so.6
#4  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7ffc0f8a7760 (LWP 7633)):
[KCrash Handler]
#6  0x00007ffc0cdc4ab5 in raise () from /lib64/libc.so.6
#7  0x00007ffc0cdc5fb6 in abort () from /lib64/libc.so.6
#8  0x00007ffc0d1bda9d in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib64/libstdc++.so.6
#9  0x00007ffc0d1bbcb6 in ?? () from /usr/lib64/libstdc++.so.6
#10 0x00007ffc0d1bbce3 in std::terminate() () from /usr/lib64/libstdc++.so.6
#11 0x00007ffc0d1bbe36 in __cxa_rethrow () from /usr/lib64/libstdc++.so.6
#12 0x00007ffc0e209bb3 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#13 0x00007ffc0e20df2b in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#14 0x000000000040416f in main ()

Possible duplicates by query: bug 280218, bug 280192, bug 280159, bug 280155, bug 280149.

Reported using DrKonqi

Comment 1 Torben Jensby Christensen 2011-08-16 22:34:28 UTC

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

kontact (4.7.0) on KDE Platform 4.7.00 (4.7.0) "release 10" using Qt 4.7.3

Another crash after start, tried to remove filters, and when re-adding spam filter it crashed

-- Backtrace (Reduced):
#12 0x00007eff2abefbb3 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#13 0x00007eff2abf3f2b in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#14 0x000000000040416f in main ()

Comment 2 Christophe Marin 2011-09-24 15:19:36 UTC

Cannot reproduce with recent versions and the backtrace doesn't really help. If you're still able to reproduce the first crash, try this :

* Install the following packages: akonadi-debuginfo, akonadi-runtime-debuginfo, kdepimlibs4-debuginfo, kontact-debuginfo, libakonadi-debuginfo, libakonadiprotocolinternals1-debuginfo, libkdepimlibs4-debuginfo

* run:
gdb --args kontact --nofork

* when the '(gdb)' prompt appears: 
start

* when the prompt reappears: 
break __cxa_rethrow

and when kontact crashes :
thread apply all bt

Comment 3 Christophe Marin 2011-09-24 16:10:03 UTC

forgot:

When done, enter 'quit'

If that doesn't give a better backtrace than the first one, retry but change:
break __cxa_rethrow

and replace it with:
catch throw

Comment 4 Torben Jensby Christensen 2011-09-26 19:06:08 UTC

(In reply to comment #2)
> Cannot reproduce with recent versions and the backtrace doesn't really help. If
> you're still able to reproduce the first crash, try this :
> 
> * Install the following packages: akonadi-debuginfo, akonadi-runtime-debuginfo,
> kdepimlibs4-debuginfo, kontact-debuginfo, libakonadi-debuginfo,
> libakonadiprotocolinternals1-debuginfo, libkdepimlibs4-debuginfo
> 
> * run:
> gdb --args kontact --nofork
> 
> * when the '(gdb)' prompt appears: 
> start
> 
> * when the prompt reappears: 
> break __cxa_rethrow
> 
> and when kontact crashes :
> thread apply all bt

I've taken multiple steps to not have my kmail crash on start-up
1) konfigured kwallet (was not configured on first try)
2) reverted back to previous kmail and removed all traces of kmail2
3) removed all filters
4) installed kamail2 again
5) removed a lot of old mails
6) disabled check for pop3 mail and scan of kmail folders on startup
7) General updated to latest versions - currently on 4.7.1

I still think it is slower and more sluggish than my old kmail was, but I only occasionally has crashes now

Regards,
Torben

Comment 5 Christophe Marin 2011-09-27 08:41:37 UTC

Nothing than can be done then. Thanks for the feedback