Various akonadi processes use 100% CPU and 200% RAM at every KDE session startup
Bug #909022 reported by
Filip Miletic (Филип Милетић)
This bug affects 11 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Akonadi |
Incomplete
|
Medium
|
|||
akonadi (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
On every KDE session startup, a bunch of akonadi-related processes are started. These start hogging the system CPU and RAM shortly after startup, and quickly tie up 100% CPU and 200% RAM (i.e. they use up almost 8G physical RAM and start chewing on swap as well!)
In order not to have my 2-core 8G RAM machine completely bogged down by these processes, I have to kill the processes manually, else my session becomes unusable and I have to reset the machine.
Ubuntu: up-to-date 11.10
Changed in akonadi: | |
importance: | Unknown → High |
status: | Unknown → New |
Changed in akonadi: | |
importance: | High → Medium |
Changed in akonadi: | |
status: | New → Incomplete |
To post a comment you must log in.
Version: unspecified (using KDE 4.7.2)
OS: Linux
More details here: https:/ /bugs.launchpad .net/ubuntu/ +source/ akonadi/ +bug/909022
On every KDE session startup, a bunch of akonadi-related processes are started. These start hogging the system CPU and RAM shortly after startup, and quickly tie up 100% CPU and 200% RAM (i.e. they use up almost 8G physical RAM and start chewing on swap as well!)
In order not to have my 2-core 8G RAM machine completely bogged down by these processes, I have to kill the processes manually, else my session becomes unusable and I have to reset the machine.
Ubuntu: up-to-date 11.10
Reproducible: Always
Steps to Reproduce:
Log into a KDE session.
Actual Results:
akonadi ties up all system resources up.
Expected Results:
akonadi should not hog CPU nor RAM.