maemo.org - Talk - Bug report: hildon-desktop cpu usage, result=causes slow battery drain

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)

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.

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.

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...

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...

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.

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.

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...

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.

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

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.