Bug 115566 - beagled burning CPU ...
Summary: beagled burning CPU ...
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Mono (show other bugs)
Version: Beta 4
Hardware: Other All
: P5 - None : Normal
Target Milestone: ---
Assignee: Gary Ekker
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-07 09:20 UTC by Michael Meeks
Modified: 2005-09-08 20:26 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
trace of nothing happening (quite busily) (42.33 KB, text/plain)
2005-09-07 09:21 UTC, Michael Meeks
Details
a patch which (at least partially) fixes this problem (3.60 KB, patch)
2005-09-08 16:45 UTC, Jon Trowbridge
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Meeks 2005-09-07 09:20:36 UTC
So - my machine is sitting idle - no files changing, it has been running all
night. Beagled should be doing nothing, and indeed strace shows it's not doing
anything substantive - however it is chewing my battery, using 0.5% of my CPU
doing essentially nothing (trace attached). It seems 'Best' is doing similar stuff.

Is this a Mono problem ? why do we need a busy loop here ? can we not wait on a
condition in the worker threads & block in poll in the mainloop ? - surely we
shouldn't be burning CPU & laptop batter to not do anything ?
Comment 1 Michael Meeks 2005-09-07 09:21:44 UTC
Created attachment 49019 [details]
trace of nothing happening (quite busily)
Comment 2 Jon Trowbridge 2005-09-08 16:45:41 UTC
Created attachment 49240 [details]
a patch which (at least partially) fixes this problem

This patch should at least help.  AFAICT this was the only place in beagle that
we were polling.
Comment 3 Gary Ekker 2005-09-08 20:26:19 UTC
Fix submitted for RC2
Comment 4 Gary Ekker 2005-09-08 20:26:44 UTC
Mark fixed