Bug 318459 - Kmail crashes on start
Summary: Kmail crashes on start
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.10.2
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-16 16:25 UTC by Andreas
Modified: 2017-01-07 21:53 UTC (History)
0 users

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 Andreas 2013-04-16 16:25:06 UTC
Application: kmail (4.10.2)
KDE Platform Version: 4.10.2
Qt Version: 4.8.3
Operating System: Linux 3.7.0-7-generic i686
Distribution: Ubuntu 12.10

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

After a few sleep/hibernate cycles and occacional use of kmail I quit the application and tried to start it again. Now, during start, it crashes repeatedly. I tried 'akonadictl restart' which did not help. I did not try reboot so far.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0xb143cb00 (LWP 2899))]

Thread 4 (Thread 0xae7f6b40 (LWP 2905)):
#0  0xb771b424 in __kernel_vsyscall ()
#1  0xb57ed96b in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:169
#2  0xb5e5a64c in __pthread_cond_wait (cond=0xb3d6d470 <WTF::pageheap_memory+20720>, mutex=0xb3d6d458 <WTF::pageheap_memory+20696>) at forward.c:139
#3  0xb36160e9 in WTF::TCMalloc_PageHeap::scavengerThread (this=this@entry=0xb3d68380 <WTF::pageheap_memory>) at wtf/FastMalloc.cpp:2499
#4  0xb36161df in WTF::TCMalloc_PageHeap::runScavengerThread (context=0xb3d68380 <WTF::pageheap_memory>) at wtf/FastMalloc.cpp:1622
#5  0xb57e9d4c in start_thread (arg=0xae7f6b40) at pthread_create.c:308
#6  0xb5e4cd3e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 3 (Thread 0xadecdb40 (LWP 2906)):
#0  0xb771b424 in __kernel_vsyscall ()
#1  0xb5e3e5f0 in __GI___poll (fds=0xad500df0, nfds=1, timeout=9866) at ../sysdeps/unix/sysv/linux/poll.c:87
#2  0xb438774b in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb4378d00 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb4378e61 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5  0xb61bc9bf in QEventDispatcherGlib::processEvents (this=0xad500468, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#6  0xb618928c in QEventLoop::processEvents (this=this@entry=0xadecd258, flags=...) at kernel/qeventloop.cpp:149
#7  0xb6189581 in QEventLoop::exec (this=0xadecd258, flags=...) at kernel/qeventloop.cpp:204
#8  0xb607468c in QThread::exec (this=this@entry=0x909ad00) at thread/qthread.cpp:501
#9  0xb60747eb in QThread::run (this=0x909ad00) at thread/qthread.cpp:568
#10 0xb6077a78 in QThreadPrivate::start (arg=0x909ad00) at thread/qthread_unix.cpp:338
#11 0xb57e9d4c in start_thread (arg=0xadecdb40) at pthread_create.c:308
#12 0xb5e4cd3e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 2 (Thread 0xad4a2b40 (LWP 2907)):
#0  0xb57ebdc8 in __pthread_mutex_lock (mutex=0xacb00550) at pthread_mutex_lock.c:92
#1  0xb5e5a864 in pthread_mutex_lock (mutex=0xacb00550) at forward.c:182
#2  0xb43b9ed0 in g_mutex_lock () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb4378bd5 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb4378e61 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5  0xb61bc9bf in QEventDispatcherGlib::processEvents (this=0xacb00468, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#6  0xb618928c in QEventLoop::processEvents (this=this@entry=0xad4a2228, flags=...) at kernel/qeventloop.cpp:149
#7  0xb6189581 in QEventLoop::exec (this=0xad4a2228, flags=...) at kernel/qeventloop.cpp:204
#8  0xb607468c in QThread::exec (this=0x90d31c8) at thread/qthread.cpp:501
#9  0xb61677dd in QInotifyFileSystemWatcherEngine::run (this=0x90d31c8) at io/qfilesystemwatcher_inotify.cpp:248
#10 0xb6077a78 in QThreadPrivate::start (arg=0x90d31c8) at thread/qthread_unix.cpp:338
#11 0xb57e9d4c in start_thread (arg=0xad4a2b40) at pthread_create.c:308
#12 0xb5e4cd3e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 1 (Thread 0xb143cb00 (LWP 2899)):
[KCrash Handler]
#7  0xb3020516 in get (this=<optimized out>) at html/parser/XSSFilter.cpp:473
#8  documentLoader (this=<optimized out>) at loader/FrameLoader.h:149
#9  WebCore::XSSFilter::init (this=0xbfa9fb44) at html/parser/XSSFilter.cpp:172
#10 0xb3d56000 in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Reported using DrKonqi
Comment 1 Denis Kurz 2016-09-24 18:15:13 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 2 Denis Kurz 2017-01-07 21:53:24 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.