Bug 230070 - System gets overloaded after Kontact start
Summary: System gets overloaded after Kontact start
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: 4.4.1
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 230827 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-03-09 10:28 UTC by GK
Modified: 2017-01-07 22:34 UTC (History)
1 user (show)

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 GK 2010-03-09 10:28:53 UTC
Version:            (using KDE 4.4.1)
Compiler:          Kubuntu 9.10 
OS:                Linux
Installed from:    Ubuntu Packages

When I start Kontakt (may be due to akonadi running), the system gets overloaded with two CPUs (Intel Core 2 Duo T8100 /2 GB) running between 75 and 98% (!), and 
physical RAM with more than 700 MiB. The system works but VERY-VERY slow for 
about 30 mins, and then all calms down. Each 15 minutes the load goes up again to 70-75%. No other software is running at the same time. 

Nepomuk strigi service was suspended as I initially thought this might be 
the issue. 

Further to that is that I can monitor this load only through a system monitor 
widget. If I open System Activity windows, I have plenty of processes listed 
with the most "heavy" of only 2% of CPU usage!  All this on a DELL inspiron 
1525 with kubuntu 9.10.
Comment 1 Christophe Marin 2011-02-01 00:22:33 UTC
*** Bug 230827 has been marked as a duplicate of this bug. ***
Comment 2 Denis Kurz 2016-09-24 19:28:04 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kontact (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 3 Denis Kurz 2017-01-07 22:34:09 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.