I had this problem with e17, and now same thing with e18
Here's powertop when I'm on batteries:
5.66 W 11.1 ms/s 269.5 Process
/usr/local/opt/google/chrome-beta/chrome --user-data-dir=/home/me
4.71 W 96.8 ms/s 224.9 Process
/usr/local/opt/google/chrome-beta/chrome --type=renderer --lang=e
4.10 W 6.6 ms/s 196.3 Interrupt PS/2 Touchpad / Keyboard
/ Mouse
1.93 W 27.7 ms/s 92.8 Process /usr/bin/enlightenment
1.21 W 1.0 ms/s 58.1 Timer hrtimer_wakeup
(ignore the watt values, but look at the wakeups).
So this isn't too bad for enlightenemnt, right?
But then I killall -STOP chrome because it's pigging my battery and I'm
not using it.
The moment I do this, enlightenment gets crazy and starts looping and
killing my battery.
Powertop now says:
8.35 W 91.2 ms/s 383.0 Process /usr/bin/enlightenment
4.52 W 5.1 ms/s 206.6 Interrupt PS/2 Touchpad / Keyboard
/ Mouse
903 mW 1.3 ms/s 41.3 Interrupt [42]
i915@pci:0000:00:02.0
Why does e18 go from 92 wakeups to 383?
Because e is started under gdb, or somesuch, I can't strace it to see
what it's doing wrong, but clearly it's spinning silly.
Can a developer try to run google-chrome, switch to batteries, start
powertop, run killall -STOP chrome, and observe?
(it will likely be faster than me relaying this via Email anyway)
Thanks,
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | PGP 1024R/763BE901
------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
enlightenment-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-users
