Bug 236379

Summary: kmail crashes after checking some gmail folders via imap and using "mark whole folder as read"
Product: [Applications] kmail Reporter: Christian Herzberg <mailchrisch>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Severity: crash    
Priority: NOR    
Version: 1.13.3   
Target Milestone: ---   
Platform: Debian unstable   
OS: Linux   
Latest Commit: Version Fixed In:

Description Christian Herzberg 2010-05-04 23:47:06 UTC
Application: kmail (1.13.3)
KDE Platform Version: 4.4.3 (KDE 4.4.3)
Qt Version: 4.6.2
Operating System: Linux 2.6.33-3.slh.5-sidux-686 i686
Distribution: Debian GNU/Linux unstable (sid)

-- Information about the crash:
I checked some old gmail folders via imap. Some had thousands of unread mails. I used the right click menu and the option "mark whole folder as read" (translated from german localization) on three folders and switch to iceweasel to read a news I opened from a mail before. After some time surfing DrKonqi told me that kmail had crashed.

Thanks for all efforts.
PS: The most bugreports DrKonqi are showing me to check for duplication are dealing with konqueror. Confusing, isn't it?

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

Thread 2 (Thread 0xb0794b70 (LWP 12376)):
#0  0xb7791424 in __kernel_vsyscall ()
#1  0xb599eb63 in __lll_lock_wait_private () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/lowlevellock.S:95
#2  0xb593391d in _L_lock_9675 () from /lib/i686/cmov/libc.so.6
#3  0xb59320d6 in *__GI___libc_free (mem=0x8bfec00) at malloc.c:3736
#4  0xb3eaac56 in IA__g_free (mem=0x8bfec00) at /build/buildd-glib2.0_2.24.1-1-i386-84Pp4V/glib2.0-2.24.1/glib/gmem.c:191
#5  0xb3ea1c6a in g_source_unref_internal (source=0x8bfec00, context=<value optimized out>, have_lock=0) at /build/buildd-glib2.0_2.24.1-1-i386-84Pp4V/glib2.0-2.24.1/glib/gmain.c:1339
#6  0xb6758e1d in ~QEventDispatcherGlib (this=0x8c01ef0, __in_chrg=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:366
#7  0xb662a4aa in QThreadPrivate::finish (arg=0xb6842370) at thread/qthread_unix.cpp:284
#8  0xb662a946 in ~__pthread_cleanup_class (arg=0xb6842370) at /usr/include/pthread.h:535
#9  QThreadPrivate::start (arg=0xb6842370) at thread/qthread_unix.cpp:253
#10 0xb46f8585 in start_thread (arg=0xb0794b70) at pthread_create.c:300
#11 0xb599129e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 1 (Thread 0xb270f700 (LWP 12272)):
[KCrash Handler]
#6  0xb7791424 in __kernel_vsyscall ()
#7  0xb58ec8e0 in *__GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#8  0xb58efe15 in *__GI_abort () at abort.c:88
#9  0xb59236c5 in __libc_message (do_abort=2, fmt=0xb59ea0e8 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:173
#10 0xb592d824 in malloc_printerr (action=2, str=0xb59ea270 "double free or corruption (out)", ptr=0x9fbed00) at malloc.c:6239
#11 0xb592f0b3 in _int_free (av=0xb5a063c0, p=0x9fbecf8) at malloc.c:4772
#12 0xb59320dd in *__GI___libc_free (mem=0x9fbed00) at malloc.c:3738
#13 0xb662508d in qFree (ptr=0x9fbed00) at global/qmalloc.cpp:60
#14 0xb673c894 in ~QMetaCallEvent (this=0xa0cc760, __in_chrg=<value optimized out>) at kernel/qobject.cpp:549
#15 0xb672f2d5 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x89b9fb8) at kernel/qcoreapplication.cpp:1361
#16 0xb672f42d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1238
#17 0xb67587ff in QCoreApplication::sendPostedEvents (s=0x89ecf10) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#18 postEventSourceDispatch (s=0x89ecf10) at kernel/qeventdispatcher_glib.cpp:276
#19 0xb3ea22f5 in g_main_dispatch (context=0x89ece90) at /build/buildd-glib2.0_2.24.1-1-i386-84Pp4V/glib2.0-2.24.1/glib/gmain.c:1960
#20 IA__g_main_context_dispatch (context=0x89ece90) at /build/buildd-glib2.0_2.24.1-1-i386-84Pp4V/glib2.0-2.24.1/glib/gmain.c:2513
#21 0xb3ea5fd8 in g_main_context_iterate (context=0x89ece90, block=<value optimized out>, dispatch=1, self=0x89e1638) at /build/buildd-glib2.0_2.24.1-1-i386-84Pp4V/glib2.0-2.24.1/glib/gmain.c:2591
#22 0xb3ea61b8 in IA__g_main_context_iteration (context=0x89ece90, may_block=1) at /build/buildd-glib2.0_2.24.1-1-i386-84Pp4V/glib2.0-2.24.1/glib/gmain.c:2654
#23 0xb67582f5 in QEventDispatcherGlib::processEvents (this=0x89b9c98, flags=...) at kernel/qeventdispatcher_glib.cpp:412
#24 0xb5d32255 in QGuiEventDispatcherGlib::processEvents (this=0x89b9c98, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#25 0xb672af09 in QEventLoop::processEvents (this=0xbfc41e14, flags=) at kernel/qeventloop.cpp:149
#26 0xb672b35a in QEventLoop::exec (this=0xbfc41e14, flags=...) at kernel/qeventloop.cpp:201
#27 0xb672f4ef in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#28 0xb5c73c87 in QApplication::exec () at kernel/qapplication.cpp:3579
#29 0x0804aafe in _start ()

Possible duplicates by query: bug 228333, bug 228223, bug 227104, bug 223957, bug 223723.

Reported using DrKonqi
Comment 1 Myriam Schweingruber 2012-08-19 11:03:45 UTC
Thank you for your report. Kmail1 is currently unmaintained and the code has changed sufficiently in Kmail2 so the backtraces are not really useful anymore. Should you experience the same crash in Kmail 4.8.5 or later, please open a new report for Kmail2. Thank you for your understanding