Version:           unknown (using KDE 3.2.2, Gentoo)
Compiler:          gcc version 3.3.2 20031218 (Gentoo Linux 3.3.2-r5, propolice-3.3-7)
OS:                Linux (i686) release 2.6.5-gentoo-r1

Yesterday I shutdown KMail (HEAD from one or two days ago) cleanly but when I tried to start it up today, it went and ate up all my box' ressources. Before my X/KDE went down completely, I was able to catch the following informations:

Relevant stuff from 'ps axfu':
| USER       PID %CPU %MEM   VSZ  RSS TTY      STAT START   TIME COMMAND
| root         1  0.9  0.0  1464   96 ?        S    13:01   0:05 init [3]
|[...]
| mss       8702 39.3 82.0 918828 423296 ?     D    13:02   3:00 kmail -session 110a0a0a0a000107686365300000219650006_1076866597_98454

An strace showed me this:
| Process 8702 attached - interrupt to quit
| --- SIGSTOP (Stopped (signal)) @ 0 (0) ---
| --- SIGSTOP (Stopped (signal)) @ 0 (0) ---
| write(2, "QGArray::at: Absolute index 9937"..., 51) = 51
| write(2, "QGArray::at: Absolute index 9937"..., 51) = 51
| write(2, "QGArray::at: Absolute index 9937"..., 51) = 51
| write(2, "QGArray::at: Absolute index 9937"..., 51) = 51
| write(2, "QGArray::at: Absolute index 9937"..., 51) = 51
|[andsoonandsoon]

And later I got from my .xsession-erros the following debug output:
| kmail: KMailApplication::newInstance()
| DCOP: unregister 'anonymous-8501'
| kdeinit: PID 8501 terminated.
| kmail: set Msg, force = true
| khtml (part): DONE: 94
| kmail: set Msg, force = true
| khtml (part): DONE: 10
| kmail: kmfolder_open == 60(1)
| kmail: KMMDict::KMDict Size: 196613
| QGArray::at: Absolute index 892108940 out of range
| QGArray::at: Absolute index 892108944 out of range
| QGArray::at: Absolute index 892108948 out of range
| QGArray::at: Absolute index 892108952 out of range
| QGArray::at: Absolute index 892108956 out of range
[[andsoonandsoon]

Till suggested to me that it looked like a corrupted index which caused this. And to change the startupFolder entry in the rc file to something else to see if that helps. The startupFolder was inbox  -- which definietely doesn't have as much messages as QGArray errors appeared.

Whatever it is, a corrupted index should not make KMail eat up all my ressources.

Changing that entry help though, leading me to another bug (which follows in a separate ticket).