Bug 160940 - hangs while eagerly eating memory
Summary: hangs while eagerly eating memory
Status: RESOLVED WORKSFORME
Alias: None
Product: kopete
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR crash
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-04-17 17:26 UTC by Andras Georgy Bekes
Modified: 2008-04-19 19:54 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andras Georgy Bekes 2008-04-17 17:26:32 UTC
Version:            (using KDE 3.5.9)
Installed from:    Debian testing/unstable Packages

When starting Kopete, it starts eating memory, without doing anything observable
-no window appears
-no output on stdout or stderr
-does not open kwallet

Memory consumption goes above 1700M VIRT and 900M RES, then slowly declines
to ~900M VIRT and ~500M RES. Then appears the window, but nothing is shown
inside the window. CPU usage is low (10-30%), probably because of thrashing.
I've always killed it after about 10 minutes of suffering (kopete does not do anything useful, while the computer is unusable because of the lack of memory).

It is 100% reproducible.

I suppose that the problem is within some library, because I can reproduce similar behaviour with kmail, however, kmail does start smoothly, I only cannot read mail.
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 kopete-kmail libraries :-( But maybe not.

I haven't (yet) found other KDE apps that behave the same.
Comment 1 Andras Georgy Bekes 2008-04-18 10:55:35 UTC
KMail bug report is Bug 160969.
Comment 2 Andras Georgy Bekes 2008-04-19 19:54:58 UTC
The problem is most probably caused by a misbehaviour of KAddressBook. 
I've filed a bug report for it (Bug 161033).