kmail crashed with SIGSEGV in QListData::begin() [on startup]

Bug #429039 reported by Yiannis Belias
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
KDE PIM
Invalid
Unknown
kdepim (Ubuntu)
Triaged
Low
Unassigned

Bug Description

Binary package hint: kdepim

Hi,
I'm testing Kubuntu Karmic alpha5 with latest packages.
I was having some strange kmail freezes where kmail was eating about 50% of both CPU cores.
I quit a couple times reopened and now it just crashed before even creating a window.
I have lots of mail ~2GB in maildir format.
Just tried to run kmail through gdb and it still crashes but I can't get a backtrace:
Starting program: /usr/bin/kmail
[Thread debugging using libthread_db enabled]
<unknown program name>(9394)/: Communication problem with "kmail" , it probably crashed.
Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" "
Program exited with code 0377.
(gdb) bt
No stack.

ProblemType: Crash
Architecture: i386
Date: Sun Sep 13 22:35:32 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/kmail
Package: kmail 4:4.3.1-0ubuntu1
ProcCmdline: /usr/bin/kmail -caption KMail
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-10.30-generic
SegvAnalysis:
 Segfault happened at: 0xedfaf2 <_ZNK11KMFolderMgr12findIdStringERK7QStringjPK11KMFolderDir+34>: mov 0x18(%eax),%edx
 PC (0x00edfaf2) ok
 source "0x18(%eax)" (0x00000024) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: kdepim
StacktraceTop:
 QListData::begin (this=0x0, folderId=..., id=0, dir=0xc)
 QList<KMFolderNode*>::constBegin (this=0x0, folderId=..., id=0, dir=0xc)
 KMFolderMgr::findIdString (this=0x0, folderId=..., id=0, dir=0xc)
 KMKernel::findFolderById (this=0xbfdb03dc, idString=...)
 KMSearch::read (this=0x9c743d0, location=...)
Title: kmail crashed with SIGSEGV in QListData::begin()
Uname: Linux 2.6.31-10-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare users

Revision history for this message
Yiannis Belias (jonnyb) wrote :
Yiannis Belias (jonnyb)
visibility: private → public
Revision history for this message
Yiannis Belias (jonnyb) wrote :

Also tried to use valgrind:
valgrind --log-file=kmail.log kmail --nofork

Revision history for this message
Yiannis Belias (jonnyb) wrote :

Hi,
I think I discovered the offending file. It's: ~/.kde/share/apps/kmail/search/Important
When I delete it, kmail works fine. When I put it back, it crashes again.
I also tried to place this file on a fresh alpha5 install on my netbook, and kmail still crashes.
I'm attaching the whole search folder.

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:KMFolderMgr::find (this=0x0, folderName=@0xbfdafad4,
KMKernel::registerSystemTrayApplet (this=0xbfdb03dc,
KMFolderSearch::canAccess (this=0x9c743d0)
KMSearch (this=0x9a6c300, parent=0x9b782c0,
KMFolderSearch::expungeContents (this=0x9a6c300)

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in kdepim (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Thanks for the very detailed bug report. I have forwarded your report on to the KMail developers. You can track this bug and correspond with the developers should they have any questions at http://bugs.kde.org/show_bug.cgi?id=207398

Changed in kdepim (Ubuntu):
importance: Medium → Low
status: New → Triaged
Changed in kdepim:
status: Unknown → Confirmed
Changed in kdepim:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.