Re: Bug report: hildon-desktop cpu usage, result=causes slow battery drain
 

That is also what I see.

I also ran a strace when hildon-desktop was more or less idle.

I'll post the strcae logs to the bug report created by carsten

Re: Bug report: hildon-desktop cpu usage, result=causes slow battery drain
 

I also see (conky/top) that hildon-desktop+xorg ~ (10-14)%cpu, but it's only when the screen is on ... when I lock the device, ssh to N900 and run top the cpu usage by these two processes is gone, so I doubt that this can cause overnight battery drain ... I can also confirm that it's still present even if I remove all widgets ... didn't tried to remove cpumem applet yet ...

[edit] yes, cpumem applet did it in my case, after removing hildon-desktop ~ 0.x %CPU

[edit1] nope, it's back again ... :-/

Re: Bug report: hildon-desktop cpu usage, result=causes slow battery drain
 

CPU usaga was very low last night, but still battery capacity drops like crazy, And the n900 was in offline mode during the night

http://marcel.mesa.nl/screenshot08.png

Re: Bug report: hildon-desktop cpu usage, result=causes slow battery drain
 

I updated bug https://bugs.maemo.org/show_bug.cgi?id=10412 with some new
tests again.

I reflashed firmware and emmc hoping this would fix it. At first It looked like it fixed it but after a short whiel the problems occured again. I did not even install new applications and removed almost everything from the desktops.

Re: Bug report: hildon-desktop cpu usage, result=causes slow battery drain
 

heres my battery graph i seem to get alot of cpu usage during idle and pretty bad battery life

running ideal 500 850
starving 250 850 -2g, wifi disabled, no bluetooth, and still has maasive cpu how do i check whats using it...

Re: Bug report: hildon-desktop cpu usage, result=causes slow battery drain
 

in xterminal you can monitor it with "top" command.

Re: Bug report: hildon-desktop cpu usage, result=causes slow battery drain
 

just checked top and nothing out of the ordinary is consuming anything

basicly what the other user has posted but i dont have corky

Xorg: ~6% (4-12%)
hildon-status-m: ~3% (2-4%)
hildon-desktop: ~2% (1-3%)

Re: Bug report: hildon-desktop cpu usage, result=causes slow battery drain
 

hmm. Normally when no windows are open (only x term) i have experienced ~3 % cpu from Xorg and all the other processes are under 1 %.

So something is not right with your device if that was on idle.

.edit
So from your processes stuff and that image i would say that your processor never sleeps. Some process constantly wakes it up. Maybe widget or some daemon on background.

Re: Bug report: hildon-desktop cpu usage, result=causes slow battery drain
 

I don't know, I'm just running the calendar widget, the media player widget, and the conversations widget. No battery issues, Xorg usually hovers around 2~3%

Re: Bug report: hildon-desktop cpu usage, result=causes slow battery drain
 

I loggedd into the n900 via the network and left the n900 screen locked.
The in the ssh sessiin I run top. When the systems is idel and running ok (e.g. no battery drain) this is the sort of process list you might expect.
A few kernel processes doing some work every now and then and the top and ssh processes.

Note that all the hildon- xxx processes use 0.0% CPU.

Now when hildon-desktop starts behaving badly you might see something like below. Hildon-desktop will be up in the top list constantly using cpu. At this time you will experience battery drain.

From the same remote login session I can trace hildon-desktop to see what it is doing.
Install the strace package: apt-get install strace

From above top output I get the process id from the hildon-desktop process. In this case process id 1275 and use that to run strace (you need to be root):

strace -t -tt -p 1275

In the first case you get hardly any output. But when you unlock the n900 screen and play around you will get output (note that your device may be a little bit less responsive). When you lock the screen again strcae output will stop (after a short while)

In the second case you will constantly get strace output like:

1276114986.251678 poll([{fd=3, events=POLLIN}, {fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=7, events=POLLIN}, {fd=8, events=POLLIN}, {fd=14, events=POLLIN}, {fd=15, events=POLLIN}, {fd=19, events=POLLIN}, {fd=13, events=POLLIN}, {fd=11, events=POLLIN}, {fd=12, events=POLLIN}], 11, 0) = 0 (Timeout)