Bug 97999 - Kontact and famd take all cpu time
Summary: Kontact and famd take all cpu time
Status: RESOLVED FIXED
Alias: None
Product: akregator
Classification: Applications
Component: kontact plugin (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-01-27 14:21 UTC by Patrick Gerken
Modified: 2005-02-23 17:19 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 Patrick Gerken 2005-01-27 14:21:39 UTC
Version:           Beta 9 (using KDE KDE 3.3.0)
Installed from:    Debian testing/unstable Packages
OS:                Linux

After some time (this changes with every start, sometimes immediatelly), kontact locks. Whole System gets nearly non responsive and top shows that kontakt takes roughly 80 % CPU Time while FAM takes 20 %. Load goes up to 5-6. 
My homedir is on NFS.
fam has no special configurations, every parameter is outcommented, there are also no special runtime parameters.
I did not yet encounter a trigger which does this behaviour. Often I am not using Kontact at the very moment and usually kagregator is not the active window. 
All Problems started with installing akregator yesterday,
and everything runs smooth again without kagregator.
I started looking if fam has an excessive number of files open on NFS, but then I saw lots of others programs use it to watch the files, so I stopped investigating in this direction.
Comment 1 Patrick Gerken 2005-02-17 22:52:01 UTC
The Bug is in the wrong section. I talked with my boss, and he mentioned similar problems without using akregator. I shouldn't have talked with him,
because now sometimes I have the same problems with PIM without akregator activated. The Bug itself is still valid, probably for PIM of FAM, but I can not change that with my permissions. So please help me ;-)
Comment 2 Allen Winter 2005-02-20 16:45:56 UTC
This sounds like what I am experiencing.  I have no idea if famd is involved or not.

I can reproduce the 80% eater by:
 click on akregator part in kontact
 after akregator is loaded click on kaddressbook part (Contacts) in kontact
Comment 3 Allen Winter 2005-02-23 17:19:44 UTC
CVS commit by winterz: 

Fix for the evil memory eater bug.
Approval from Coolo and Will.
Sorry for blaming Akregator which had absolutely nothing to do with this bug.
BUGS: 97999


  M +7 -5      contactlistview.cpp   1.14


--- kdepim/kaddressbook/views/contactlistview.cpp  #1.13:1.14
@@ -224,8 +224,10 @@ void ContactListViewItem::refresh()
   int i = 0;
   // don't show unknown presence, it's not interesting
-  if ( mHasIM && mIMProxy->presenceNumeric( mAddressee.uid() ) > 0 )
+  if ( mHasIM ) {
+    if ( mIMProxy->presenceNumeric( mAddressee.uid() ) > 0 )
     setPixmap( parentListView->imColumn(), mIMProxy->presenceIcon( mAddressee.uid() ) );
   else
     setPixmap( parentListView->imColumn(), QPixmap() );
+  }
 
   KABC::Field::List::ConstIterator it;