maemo.org - Talk
Page 1 of 4 1 23 Last »
Show 40 post(s) from this thread on one page

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Nokia N900 (https://talk.maemo.org/forumdisplay.php?f=44)
-   -   Bug report: hildon-desktop cpu usage, result=causes slow battery drain (https://talk.maemo.org/showthread.php?t=54462)

CarstenDutch 2010-05-29 16:44
Bug report: hildon-desktop cpu usage, result=causes slow battery drain
 
I'am examine the cause at the moment and still adding reports.

SOFTWARE VERSION:
Newly flashed PR1.2,
RX-51_2009SE_10.2010.19-1_PR_COMBINED_MR0_ARM
RX-51_2009SE_10.2010.13-2.VANILLA_PR_EMMC_MR0_ARM

EXACT STEPS LEADING TO PROBLEM:
1.
2.
3.

EXPECTED OUTCOME:

ACTUAL OUTCOME:

REPRODUCIBILITY:
None yet

EXTRA SOFTWARE INSTALLED:
Extras-devel repository enabled,
Enhanced Linux kernel for power users v37 [non-overclocked]

Affect hildon-status-menu,
Simple Brightness Applet
3G/2G/Dual Mode Selection Applet
Load Applet

Affect hildon-desktop,
Recaller

OTHER COMMENTS:
Using 1 desktop and 3 turned off.
hildon-desktop sometimes in conjunction with Xorg both 15% usage seen in ''top'' (used ''top'' for less graphics intense view wrt Xorg)

Reported bug: https://bugs.maemo.org/show_bug.cgi?id=10412

Jaco2k 2010-05-29 16:53
Re: Bug report: hildon-desktop cpu usage, result=causes slow battery drain
 
I confirm this and will vote for it. Some might blame it on widgets but the exact same widget set pre-PR1.2 did not cause it.

das_schlumpfie 2010-05-29 17:02
Re: Bug report: hildon-desktop cpu usage, result=causes slow battery drain
 
thanks for this post, now i know why my n900 didnt last 3 hours today.

Metalov 2010-05-29 17:39
Re: Bug report: hildon-desktop cpu usage, result=causes slow battery drain
 
Same thing here, hildon-desktop using about 15% cpu all the time.

kevinm2k 2010-05-29 17:46
Re: Bug report: hildon-desktop cpu usage, result=causes slow battery drain
 
I have had same issue, i've reflashed mine about 3 times now,this time I tried installing things slowly, without anything it wasn't too bad, the second I installed the facebook widget things went downhill... it seems I can't have the same things open and have a decent battery life. But seems good without.

mikkov 2010-05-29 18:10
Re: Bug report: hildon-desktop cpu usage, result=causes slow battery drain
 
People who have this problems should list all widgets they are running, otherwise this leads nowhere.

PsychoModr 2010-05-29 20:08
Re: Bug report: hildon-desktop cpu usage, result=causes slow battery drain
 
hildon-desktop first give me 20% load continu, phone didn't last for 2hours, reflashed but manually, now it's fione, hildon-desktop uses2.33%

only rises when i receive sms or something else, and goes back down after received message.

over the air update didn't go well, so i flashed manually, works best for me.
Think that over the air update are bugs in

ZogG 2010-05-29 20:16
Re: Bug report: hildon-desktop cpu usage, result=causes slow battery drain
 
as i assume it's copy from bug you ent to bugzilla, if not - please send it to bugzilla and if yes, we would liek to have link to it as well.

ossipena 2010-05-29 20:29
Re: Bug report: hildon-desktop cpu usage, result=causes slow battery drain
 
the title is stupid. even shutting device down and removing battery causes slow battery drain...

disable all the widgets and check how much hildon-desktop stresses cpu. if it is significantly lower then add widgets etc one after another and you'll know to which component the bug should be reported.

the bugreport described above helps no-one and causes certain people to keep asking more and more things that could have reported in the beginning when a bit common sense would have used.

CarstenDutch 2010-05-29 20:45
Re: Bug report: hildon-desktop cpu usage, result=causes slow battery drain
 
Quote:
Originally Posted by ossipena (Post 688662)
the title is stupid. even shutting device down and removing battery causes slow battery drain...

disable all the widgets and check how much hildon-desktop stresses cpu. if it is significantly lower then add widgets etc one after another and you'll know to which component the bug should be reported.

the bugreport described above helps no-one and causes certain people to keep asking more and more things that could have reported in the beginning when a bit common sense would have used.
I don't want to comment on the word "stupid"

If a process is taking aprox 15% cpu load for a to long time it won't be the same if anybody shutdown the device and removing the battery causes slow battery drain...

This is still a problem to look at.

MaBeef 2010-06-01 19:06
Re: Bug report: hildon-desktop cpu usage, result=causes slow battery drain
 
I also wanted to confirm this bug. The only widget I even run is "personal IP address". I've also had hildon-desktop eat 6% cpu even without any widgets running at all.

ossipena, this is definitely a real problem if it's causing my battery to drain faster than it did during the last release, despite all the battery drain bug fixes in this release.

nithin 2010-06-01 19:41
Re: Bug report: hildon-desktop cpu usage, result=causes slow battery drain
 
I had the problem with hildon cpu usage prior to the P.R 1.2 update. Maybe cause i was running the Matrix theme. Not sure though. I do have the Dataplan monitor widget installed. The CPU usage use to go high after like 24 hours of keeping the device on and so was the memory usage. If i restarted it, it would be fine for the next 24 hours. Currently i have not installed the Matrix theme but i have all the other widgets installed and i dont have this problem any more.

rolan900d 2010-06-01 19:49
Re: Bug report: hildon-desktop cpu usage, result=causes slow battery drain
 
Uninstall load applet and quick lanch made my CPU hildon destop drop from 14% to 3%

To be honest i didn't use those apps that much....
Pleased now....

By the way; I run matrix theme with animated matrix live wallpaper...
So that is not a problem!
When screen is locked the animation stops...

mirakels 2010-06-02 18:58
Re: Bug report: hildon-desktop cpu usage, result=causes slow battery drain
 
I see the same thing with hildon-desktop.
One or more reboots often help.

I just isntalled the strace tool. When hildon-desktop strts using cpu again I'll try strace on it hoping to see what it is doing...

pyromaniac 2010-06-02 19:14
Re: Bug report: hildon-desktop cpu usage, result=causes slow battery drain
 
is this the same as ...
[Bug 8723] items become totally non-responsive for no reason
https://bugs.maemo.org/show_bug.cgi?id=8723
?
have had this problem since always. Not upgraded to PR1.2 yet so cant comment on difference.

Catacylsm 2010-06-02 19:17
Re: Bug report: hildon-desktop cpu usage, result=causes slow battery drain
 
Using 4 desktops with 3/4 with widgets on, im having great battery life even with them on but i will probably change this to see if i can extend it even more,

I created the phenominal battery life 1.2 thread and people are both reporting battery changes as good or the same, nothing bad yet :D.

sga 2010-06-02 21:50
Re: Bug report: hildon-desktop cpu usage, result=causes slow battery drain
 
I've been so happy with my N900 - until after the Maemo update. Now suddenly my battery is drained quite rapidly. I thought my battery was broke and have already ordered a new one. But my colleague just tells me, he's facing the same problem now. Phone also suddenly gets unresponsive for a few secs.

Please, please fix this bug. Never before had an update that actually adds problems instead of removing them...

Austinek 2010-06-02 23:25
Re: Bug report: hildon-desktop cpu usage, result=causes slow battery drain
 
Same bug here.. hildon-desktop using about 5-10% cpu.
For me, the problem was in the foreca weather widget.

mirakels 2010-06-03 14:12
Re: Bug report: hildon-desktop cpu usage, result=causes slow battery drain
 
hildon-desktop went off again.... I ran an strace. All that it is doin is looping around polling file descriptors. Most of the time the poll times out.

Code:
    0.000000 restart_syscall(<... resuming interrupted call ...>) = 1
    0.001068 ioctl(8, FIONREAD, [32])  = 0
    0.000458 read(8, "`\3\206s5\0 \4\215\5\0\2\276\371\323\0\0\0\0\0 \3\250\1\0\0008\0 \3\250\1", 32) = 32
    0.001007 write(8, "\220\5\2\0g\f\0\2\224\3\4\0\215\5\0\2\0\0\0\0g\f\0\2\220\23\2\0g\f\0\2", 32) = 32
    0.000580 read(8, 0xbe8a9e78, 32)  = -1 EAGAIN (Resource temporarily unavailable)
    0.000488 poll([{fd=8, events=POLLIN}], 1, -1) = 1 ([{fd=8, revents=POLLIN}])
    0.000915 read(8, "\1\240\211s\2\0\0\0\0\0\0\0\30\3b\1\0\0K\1\1\0a\1\f\0K\1\r\0a\1", 32) = 32
    0.000458 read(8, "\0\0\0\0\30\3b\1", 8) = 8
    0.000580 write(8, "\220\n\2\0g\f\0\2", 8) = 8
    0.000366 ioctl(8, FIONREAD, [0])  = 0
    0.000366 ioctl(7, FIONREAD, [0])  = 0
    0.000306 ioctl(8, FIONREAD, [0])  = 0
    0.000335 gettimeofday({1275563523, 127809}, NULL) = 0
    0.000336 clock_gettime(CLOCK_MONOTONIC, {13892, 67051181}) = 0
    0.000305 poll([{fd=5, events=POLLIN}, {fd=4, events=POLLIN}, {fd=7, events=POLLIN}, {fd=8, events=POLLIN}, {fd=17, events=POLLIN}, {fd=18, events=POLLIN}, {fd=3, events=POLLIN}, {fd=19, events=POLLIN}, {fd=16, events=POLLIN}, {fd=14, events=POLLIN}, {fd=15, events=POLLIN}], 11, 0) = 0 (Timeout)
    0.000519 gettimeofday({1275563523, 128939}, NULL) = 0
    0.000641 gettimeofday({1275563523, 129579}, NULL) = 0
    0.000580 ioctl(7, FIONREAD, [0])  = 0
    0.000335 ioctl(8, FIONREAD, [0])  = 0
    0.000306 gettimeofday({1275563523, 130800}, NULL) = 0
    0.000305 clock_gettime(CLOCK_MONOTONIC, {13892, 70011386}) = 0
    0.000274 poll([{fd=5, events=POLLIN}, {fd=4, events=POLLIN}, {fd=7, events=POLLIN}, {fd=8, events=POLLIN}, {fd=17, events=POLLIN}, {fd=18, events=POLLIN}, {fd=3, events=POLLIN}, {fd=19, events=POLLIN}, {fd=16, events=POLLIN}, {fd=14, events=POLLIN}, {fd=15, events=POLLIN}], 11, 0) = 0 (Timeout)
    0.000672 ioctl(7, FIONREAD, [0])  = 0
    0.000305 ioctl(8, FIONREAD, [0])  = 0
    0.000305 gettimeofday({1275563523, 132662}, NULL) = 0
    0.000275 clock_gettime(CLOCK_MONOTONIC, {13892, 71872960}) = 0
    0.000305 poll([{fd=5, events=POLLIN}, {fd=4, events=POLLIN}, {fd=7, events=POLLIN}, {fd=8, events=POLLIN}, {fd=17, events=POLLIN}, {fd=18, events=POLLIN}, {fd=3, events=POLLIN}, {fd=19, events=POLLIN}, {fd=16, events=POLLIN}, {fd=14, events=POLLIN}, {fd=15, events=POLLIN}], 11, 12) = 0 (Timeout)
    0.012939 gettimeofday({1275563523, 146181}, NULL) = 0
    0.000275 clock_gettime(CLOCK_MONOTONIC, {13892, 85392247}) = 0
    0.000336 gettimeofday({1275563523, 146761}, NULL) = 0
    0.000641 gettimeofday({1275563523, 147432}, NULL) = 0
    0.000580 ioctl(7, FIONREAD, [0])  = 0
    0.000335 ioctl(8, FIONREAD, [0])  = 0
    0.000336 gettimeofday({1275563523, 148653}, NULL) = 0
    0.000275 clock_gettime(CLOCK_MONOTONIC, {13892, 87864172}) = 0
    0.000274 poll([{fd=5, events=POLLIN}, {fd=4, events=POLLIN}, {fd=7, events=POLLIN}, {fd=8, events=POLLIN}, {fd=17, events=POLLIN}, {fd=18, events=POLLIN}, {fd=3, events=POLLIN}, {fd=19, events=POLLIN}, {fd=16, events=POLLIN}, {fd=14, events=POLLIN}, {fd=15, events=POLLIN}], 11, 0) = 0 (Timeout)
    0.000580 ioctl(7, FIONREAD, [0])  = 0
    0.000305 ioctl(8, FIONREAD, [0])  = 0
    0.000305 gettimeofday({1275563523, 150392}, NULL) = 0
    0.000275 clock_gettime(CLOCK_MONOTONIC, {13892, 89603674}) = 0
    0.000275 poll([{fd=5, events=POLLIN}, {fd=4, events=POLLIN}, {fd=7, events=POLLIN}, {fd=8, events=POLLIN}, {fd=17, events=POLLIN}, {fd=18, events=POLLIN}, {fd=3, events=POLLIN}, {fd=19, events=POLLIN}, {fd=16, events=POLLIN}, {fd=14, events=POLLIN}, {fd=15, events=POLLIN}], 11, 10) = 0 (Timeout)
    0.010864 gettimeofday({1275563523, 161837}, NULL) = 0
    0.000275 clock_gettime(CLOCK_MONOTONIC, {13892, 101047766}) = 0
    0.000305 gettimeofday({1275563523, 162416}, NULL) = 0
    0.000610 gettimeofday({1275563523, 163027}, NULL) = 0
    0.000549 ioctl(7, FIONREAD, [0])  = 0
    0.000336 ioctl(8, FIONREAD, [0])  = 0
    0.000305 gettimeofday({1275563523, 164217}, NULL) = 0
    0.000428 clock_gettime(CLOCK_MONOTONIC, {13892, 103580726}) = 0

MaBeef 2010-06-03 19:53
Re: Bug report: hildon-desktop cpu usage, result=causes slow battery drain
 
I have on occasion seen hildon-desktop drop down to and stay at around 0.33% cpu usage. So it is kind of a random problem it seems and maybe not related to which widgets are running.

My battery life is so bad right now that I went to bed last night with my phone at 50% charge and not running anything and found it completely dead when I woke up.

mirakels 2010-06-04 10:22
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

daniel.gazda 2010-06-04 11:30
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 ... :-/

mirakels 2010-06-05 08:01
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

mirakels 2010-06-10 07:58
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.

bman 2010-06-10 09:02
Re: Bug report: hildon-desktop cpu usage, result=causes slow battery drain
 
1 Attachment(s)
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...

slender 2010-06-10 09:10
Re: Bug report: hildon-desktop cpu usage, result=causes slow battery drain
 
in xterminal you can monitor it with "top" command.

bman 2010-06-10 09:17
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%)

slender 2010-06-10 09:26
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.

rickysio 2010-06-10 09:27
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%

mirakels 2010-06-10 10:42
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.

Code:
Mem: 230684K used, 14664K free, 0K shrd, 9408K buff, 67884K cached
CPU:  0.3% usr  3.2% sys  0.0% nice 95.9% idle  0.0% io  0.0% irq  0.3% softirq
Load average: 0.00 0.00 0.00
  PID  PPID USER    STAT  RSS %MEM %CPU COMMAND
  27    2 root    RW      0  0.0  1.1 [kondemand/0]
 2327  2318 user    R      740  0.3  0.9 top
  10    2 root    SW      0  0.0  0.9 [omap2_mcspi]
 2317  2315 user    S    1356  0.5  0.7 sshd: user@pts/0 
  469    2 root    SW      0  0.0  0.1 [wl12xx]
 1778  1275 user    S    18124  7.3  0.0 /opt/BatteryGraph/bin/BatteryGraph
 1272  1174 user    S    17892  7.2  0.0 /usr/bin/hildon-home                                                     
 1008  682 root    S <  14888  6.0  0.0 /usr/bin/Xorg -logfile /tmp/Xorg.0.log -logverbose 1 -nolisten tcp -noreset -s 0 -core
 1681  1315 user    S    12524  5.0  0.0 /usr/sbin/browserd -s 1681 -n RTComMessagingServer
 1672  1174 user    S    11496  4.6  0.0 /usr/bin/rtcom-call-ui                                                   
 1275  1174 user    S    10704  4.3  0.0 /usr/bin/hildon-desktop                                                   
 1705  1174 user    S    10400  4.2  0.0 /usr/bin/image-viewer                                                     
 1266  1174 user    S    10376  4.2  0.0 /usr/bin/hildon-status-menu                                               
  682    1 root    S <  9552  3.8  0.0 /sbin/dsme -p /usr/lib/dsme/libstartup.so
 1714  1174 user    S    8924  3.6  0.0 /usr/bin/modest                                                           
                                                       
 1699  1315 user    S    8748  3.5  0.0 /usr/sbin/browserd -s 1699 -n browserui
 1677  1174 user    S    7540  3.0  0.0 /usr/bin/rtcom-messaging-ui                                               
 1668  1174 user    S    7328  2.9  0.0 /usr/bin/osso-addressbook
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.

Code:
Mem: 230684K used, 14664K free, 0K shrd, 9408K buff, 67884K cached
CPU:  4.3% usr  3.2% sys  0.0% nice 91.9% idle  0.0% io  0.0% irq  0.3% softirq
Load average: 0.00 0.00 0.00
  PID  PPID USER    STAT  RSS %MEM %CPU COMMAND
 1275  1174 user    S    10704  4.3  3.9 /usr/bin/hildon-desktop
  27    2 root    RW      0  0.0  1.1 [kondemand/0]
 2327  2318 user    R      740  0.3  0.9 top
  10    2 root    SW      0  0.0  0.9 [omap2_mcspi]
 2317  2315 user    S    1356  0.5  0.7 sshd: user@pts/0 
  469    2 root    SW      0  0.0  0.1 [wl12xx]
 1778  1275 user    S    18124  7.3  0.0 /opt/BatteryGraph/bin/BatteryGraph
 1272  1174 user    S    17892  7.2  0.0 /usr/bin/hildon-home                                                     
 1008  682 root    S <  14888  6.0  0.0 /usr/bin/Xorg -logfile /tmp/Xorg.0.log -logverbose 1 -nolisten tcp -noreset -s 0 -core
 1681  1315 user    S    12524  5.0  0.0 /usr/sbin/browserd -s 1681 -n RTComMessagingServer
 1672  1174 user    S    11496  4.6  0.0 /usr/bin/rtcom-call-ui                                                   
 1705  1174 user    S    10400  4.2  0.0 /usr/bin/image-viewer                                                     
 1266  1174 user    S    10376  4.2  0.0 /usr/bin/hildon-status-menu                                               
  682    1 root    S <  9552  3.8  0.0 /sbin/dsme -p /usr/lib/dsme/libstartup.so
 1714  1174 user    S    8924  3.6  0.0 /usr/bin/modest
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)

smoku 2010-06-10 10:55
Re: Bug report: hildon-desktop cpu usage, result=causes slow battery drain
 
Quote:
Originally Posted by bman (Post 708435)
just checked top and nothing out of the ordinary is consuming anything
Standard 'top' is not well suited for this. You should be using 'powertop' tool.
http://talk.maemo.org/showpost.php?p...3&postcount=21

daperl 2010-06-10 10:59
Re: Bug report: hildon-desktop cpu usage, result=causes slow battery drain
 
I think Load Applet (this also goes for cpumem) isn't listening for or respecting the "status bar not visible" messages. While it was installed and the status bar wasn't present, top was reporting hildon-status-menu at a constant .7% and Xorg over 3%. Uninstalled, hildon-status-menu is back down to 0% and Xorg hovers near .9% (probably because of top updates). If someone doesn't take a look at Load Applet and cpumem within the next week, I will.

Chrome 2010-06-10 11:03
Re: Bug report: hildon-desktop cpu usage, result=causes slow battery drain
 
Quote:
Originally Posted by smoku (Post 708584)
Standard 'top' is not well suited for this. You should be using 'powertop' tool.
http://talk.maemo.org/showpost.php?p...3&postcount=21
Hey smoku, how to open power top?

Also is it better than htop?

daperl 2010-06-10 11:18
Re: Bug report: hildon-desktop cpu usage, result=causes slow battery drain
 
Oh, and by the way, the same goes for home widgets and other visual apps. They also need to listen for and respect the "not visible" messages.

slender 2010-06-10 11:30
Re: Bug report: hildon-desktop cpu usage, result=causes slow battery drain
 
if you end up runnin powertop do it following way

-close all apps
-open x-term and run it and before it starts do(there is little delay before monitoring starts):
-minimize window and go to desktop view
-switch n900 to locked state (screen off) and leave it on table for couple of minutes


-open it and post results/analyze it. You should be able to see states where cpu is and what process possibly wakes processor from sleep.

mirakels 2010-06-10 12:14
Re: Bug report: hildon-desktop cpu usage, result=causes slow battery drain
 
Hildon-desktop just went crazy again. I already save a powertop output when it was running fine. Now I took a powertop again. See the attachments in the bug report.

flailingmonkey 2010-06-10 12:51
Re: Bug report: hildon-desktop cpu usage, result=causes slow battery drain
 
Note that all the source for hildon-desktop is freely available at http://maemo.gitorious.org/fremantle-hildon-desktop in case anyone wants to dive right into the code.

menno 2010-06-10 18:29
Re: Bug report: hildon-desktop cpu usage, result=causes slow battery drain
 
I can confirm I'm having the same problem. Uninstalling cpumem-applet has made things slightly better for me, in that it happens less frequently now, but I still get the hildon-desktop process occasionally idling with high cpu of about 12%

Inacurate 2010-06-10 21:07
Re: Bug report: hildon-desktop cpu usage, result=causes slow battery drain
 
I was running into <4 hours of battery life AND the backside getting extremely warm - I have removed the Facebook Widget from my homescreen(have 4 enabled) and no warm backside and thus far still plenty of battery life left while being connected to Wi-Fi all day like I was when it was draining.

andy82i 2010-06-10 21:13
Re: Bug report: hildon-desktop cpu usage, result=causes slow battery drain
 
I can confirm the same problem, had hildon-desktop showing around 12% in Conky & htop, lots of CPU use in idle & fast battery drain shown by BatteryGraph.
I noticed it today after installing Catorise last night. Removed it this evening & on observing the hildon-desktop process in Conky, it will occasionally show 0.33% CPU, with very rare peaks reaching 1%.


All times are GMT. The time now is 16:02.
Page 1 of 4 1 23 Last »
Show 40 post(s) from this thread on one page

vBulletin® Version 3.8.8