Bug 160969

Summary:	hangs while eagerly eating memory before crashing
Product:	[Unmaintained] kmail	Reporter:	Andras Georgy Bekes <bekesa>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED WORKSFORME
Severity:	crash
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Debian testing
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Andras Georgy Bekes 2008-04-18 10:53:22 UTC

Version:            (using KDE 3.5.9)
Installed from:    Debian testing/unstable Packages

KMail starts up normally. Does connect to IMAP server normally and indexes mails normally. After clicking on a mail, its memory consumption constantly increases without doing anything observable. CPU usage is low (5-30%), probably because of thrashing.

After it eats 2000M VIRT memory, dies (not unexpectedly) with the following message:
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc
*** KMail got signal 6 (Crashing)
KCrash: Application 'kmail' crashing...
 
It is 100% reproducible, and does the same when reading local mail(dir) or IMAP.

I suppose that the problem is within some library, because I can reproduce similar behaviour with kopete, however, kopete does this right after starting it, even before creating its window or opening kwallet.

The two problems started at the same time, probably after upgrading to the bogus library version.
 
How can I check which debian packages were updated in the last 2-3 days? 
I remember there was an upgrade of several kde-related packages that probably contained upgrades of all the common kopete-kmail libraries :-( But maybe not. 
 
I haven't (yet) found other KDE apps that behave the same.

Kopete bug report is Bug 160940.

Comment 1 Andras Georgy Bekes 2008-04-19 17:05:32 UTC

Just to make the above clear: currently my KMail starts with opening a mail folder that happens to be empty, so it does not try to show me a mail at s

I also have a new way to reproduce the faulty behaviour:
Instead of clicking on a non-empty folder, I start writing a new mail. In the "Composer" window, everything works, except for the "To:" field. Whenever I start typing in that field, memory eating starts.
Maybe the fault is addressbook-related?

I've tried, Kaddressbook starts eating memory immediately when I start it...

Comment 2 Andras Georgy Bekes 2008-04-19 19:52:23 UTC

The problem is most probably caused by a misbehaviour of KAddressBook.
I've filed a bug report for it (Bug 161033).