Bug 249997 - kmail 2 beta 1 - crash on close
Summary: kmail 2 beta 1 - crash on close
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 2.0.90
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-03 13:13 UTC by mps
Modified: 2010-12-11 21:39 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mps 2010-09-03 13:13:23 UTC
Application: kmail (2.0 beta1)
KDE Platform Version: 4.5.1 (KDE 4.5.1)
Qt Version: 4.7.0
Operating System: Linux 2.6.34.6-47.fc13.x86_64 x86_64
Distribution (Platform): Fedora RPMs

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

Kmail 2 crashed on close with attached backtrace. prior to me closing it two strange things were happening: 1) more than one menu item remained greyed out as if selected (Tools, Settings and Go) and 2) a fragment of text remained in the filter box that I could not select or delete but which was not filtering the messages.

The crash can be reproduced some of the time.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
82	T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[Current thread is 1 (Thread 0x7fa6e187b820 (LWP 24751))]

Thread 3 (Thread 0x7fa6cffff710 (LWP 24775)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x000000337180cb4e in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib64/libQtWebKit.so.4
#2  0x000000337180cc69 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/libQtWebKit.so.4
#3  0x00000030de607761 in start_thread (arg=0x7fa6cffff710) at pthread_create.c:301
#4  0x00000030ddae14ed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 2 (Thread 0x7fa698c3a710 (LWP 24895)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007fa6cd7811e2 in LoopRequest (data=0xb18fbe0) at playlist/thread.c:539
#2  Thread (data=0xb18fbe0) at playlist/thread.c:586
#3  0x00000030de607761 in start_thread (arg=0x7fa698c3a710) at pthread_create.c:301
#4  0x00000030ddae14ed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 1 (Thread 0x7fa6e187b820 (LWP 24751)):
[KCrash Handler]
#6  __pthread_mutex_lock (mutex=0x474e4950) at pthread_mutex_lock.c:50
#7  0x00000030e0649da7 in XrmDestroyDatabase (db=0x13b4520) at Xrm.c:2642
#8  0x00000030e063476d in _XFreeDisplayStructure (dpy=0x1398430) at OpenDis.c:839
#9  0x00000030e061fcbf in XCloseDisplay (dpy=0x1398430) at ClDisplay.c:82
#10 0x0000003368821ef5 in qt_cleanup () at kernel/qapplication_x11.cpp:2638
#11 0x00000033687be4d0 in QApplication::~QApplication (this=0x7fff60c24110, __in_chrg=<value optimized out>) at kernel/qapplication.cpp:1121
#12 0x0000000000402f88 in ~KMailApplication (argc=<value optimized out>, argv=<value optimized out>) at /usr/src/debug/kdepim-4.4.93/kmail/main.cpp:43
#13 main (argc=<value optimized out>, argv=<value optimized out>) at /usr/src/debug/kdepim-4.4.93/kmail/main.cpp:149

Reported using DrKonqi
Comment 1 Myriam Schweingruber 2010-10-17 00:20:45 UTC
Same backtrace as bug 240001, and reported with various KDE applications.
Comment 2 Tobias Koenig 2010-12-11 21:39:32 UTC
Hej,

I can't reproduce it here and don't see any KMail specific code involved in the backtrace. So according to Myriam's comment it's not a KMail problem.

Ciao,
Tobias