Bug 179597

Summary: Crashes when I select 'Apply All Filters'
Product: [Unmaintained] kmail Reporter: Declan McGrath <subs>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED REMIND    
Severity: crash CC: christophe
Priority: NOR    
Version: 1.10.3   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Declan McGrath 2009-01-04 13:30:25 UTC
Version:           1.10.3 (using KDE 4.1.3)
Compiler:          g++ (Ubuntu 4.3.2-1ubuntu11) 4.3.2 
OS:                Linux
Installed from:    Ubuntu Packages

I highlighted all messages in my inbox and then elected to 'Apply All Filters'. Kmail hung and when I ran the 'top' command in a terminal, I saw clamscan running at around 90% CPU usage. Eventually Kmail crashed and I got the following backtrace

Application: KMail (kmail), signal SIGSEGV
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb41bd6c0 (LWP 15881)]
[New Thread 0xb1159b90 (LWP 15904)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6  0xb6822913 in ?? () from /usr/lib/libQtGui.so.4
#7  0xb68219e5 in QApplication::x11ProcessEvent () from /usr/lib/libQtGui.so.4
#8  0xb684b7aa in ?? () from /usr/lib/libQtGui.so.4
#9  0xb63766f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#10 0xb6379da3 in ?? () from /usr/lib/libglib-2.0.so.0
#11 0xb6379f61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#12 0xb7eec478 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#13 0xb684aea5 in ?? () from /usr/lib/libQtGui.so.4
#14 0xb7ec052a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#15 0xb7ec06ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#16 0xb7ec2da5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#17 0xb67b0767 in QApplication::exec () from /usr/lib/libQtGui.so.4
#18 0x0804a6c0 in _start ()
#0  0xb7fdf430 in __kernel_vsyscall ()
Comment 1 Jaime Torres 2009-01-04 13:36:01 UTC
If you can reproduce the crash at will, could you read
http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
and post a complete backtrace here? Thanks 
Comment 2 Christophe Marin 2009-02-14 19:14:54 UTC
Closing due to lack of feedback (Comment #1).