Bug 107279

Summary: kmail crashes when searching in all local messages: too many open files
Product: [Applications] kmail Reporter: BORGULYA Gábor <bugs2>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED WORKSFORME    
Severity: crash    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Gentoo Packages   
OS: Linux   
Latest Commit: Version Fixed In:

Description BORGULYA Gábor 2005-06-12 16:35:27 UTC
Version:            (using KDE KDE 3.3.0)
Installed from:    Gentoo Packages
Compiler:          GCC 3.3.3 20040412 CFLAGS="-O3 -march=pentium4 -fomit-frame-pointer -pipe"
OS:                Linux

When I search for a term in all local messages, KMail is reading the HDD for 20 minutes, keeping the processor at 40% (Pentium4), finally crashes:
too many open files.
Comment 1 BORGULYA Gábor 2005-06-12 16:36:53 UTC
Using host libthread_db library "/lib/libthread_db.so.1".
0x4e7c0008 in waitpid ()
   from /lib/libpthread.so.0
#0  0x4e7c0008 in waitpid () from /lib/libpthread.so.0
#1  0x4f58b1d8 in ?? () from /usr/kde/3.3/lib/libkdecore.so.4
#2  0x4f4acb97 in KCrash::defaultCrashHandler(int) ()
   from /usr/kde/3.3/lib/libkdecore.so.4
#3  0x0000000c in ?? ()
#4  0x4f3458a4 in ?? () from /usr/qt/3/lib/libqt-mt.so.3
#5  0xbfffe218 in ?? ()
#6  0xbfffe210 in ?? ()
#7  0x081779d0 in ?? ()
#8  0x4f3458a4 in ?? () from /usr/qt/3/lib/libqt-mt.so.3
#9  0x4f53ce80 in malloc () from /usr/kde/3.3/lib/libkdecore.so.4
#10 0x0000000e in ?? ()
#11 0x00006d54 in ?? ()
#12 0x00000400 in ?? ()
#13 0x00000400 in ?? ()
#14 0x0000006c in ?? ()
#15 0x00000001 in ?? ()
Comment 2 BORGULYA Gábor 2005-06-12 17:06:25 UTC
Running the search again I observed that the crash occured when the counter of processed messages was between 105'000 and 130'000.
Comment 3 Philip Rodrigues 2006-09-18 12:26:51 UTC
Does this problem still exist in KDE 3.5?
Comment 4 BORGULYA Gábor 2006-10-16 18:53:29 UTC
I ran a search with KMail 1.9.1 (KDE 3.5.2) and it did not crash.
Comment 5 Philip Rodrigues 2006-10-16 23:27:19 UTC
OK, please reopen this bug if the problem returns