Running Chromium 49 (Debian's 49.0.2623.108-1~deb8u1) and finding I am getting a baseline 100hz wakeup.  This does show up in PowerTOP, though you can use /proc/timer_stats to drill in further, as I show below.

This happens regardless of whether I start Chrome with a single empty tab, or I have ten tabs open all with differing things, that 'SCTP timer' is locked at 100hz.  Points of interest:

 * you only get a new SCTP timer per user profile
 * the SCTP timer is only on one of the group of children processes

----
# echo 1 > /proc/timer_stats
# watch -n1 'cat /proc/timer_stats | sort -k1,1nr | head'
4494 total events, 501.730 events/sec
  884,  9477 SCTP timer       schedule_hrtimeout_range_clock (hrtimer_wakeup) <--- 100hz
  300,     0 swapper/1        tick_nohz_restart (tick_sched_timer)
  286,     7 rcu_sched        rcu_gp_kthread (process_timeout)
  276,     0 swapper/0        tick_nohz_restart (tick_sched_timer)
  226,  9274 xterm            schedule_hrtimeout_range_clock (hrtimer_wakeup)
  223,     0 swapper/2        tick_nohz_restart (tick_sched_timer)
  196,     0 swapper/3        tick_nohz_restart (tick_sched_timer)
  179,  4892 offlineimap      schedule_hrtimeout_range_clock (hrtimer_wakeup)
  179,  4902 offlineimap      schedule_hrtimeout_range_clock (hrtimer_wakeup)
# echo 0 > /proc/timer_stats
----
$ ps -eLf --cols=50 | grep 9477
alex      9387  9335  9477  0   16 08:44 ?        00:00:00 /usr/lib/chromium/chromium --type=rendere

$ ps axf --cols=100
 9319 ?        S      0:00 /bin/bash
 9321 ?        Sl     0:11  \_ /usr/lib/chromium/chromium --ppapi-flash-path=/usr/lib/pepperflashplu
 9332 ?        S      0:00      \_ /usr/lib/chromium/chrome-sandbox /usr/lib/chromium/chromium --typ
 9333 ?        S      0:00      |   \_ /usr/lib/chromium/chromium --type=zygote --ppapi-flash-path=/
 9335 ?        S      0:00      |       \_ /usr/lib/chromium/chromium --type=zygote --ppapi-flash-pa
 9370 ?        Sl     0:00      |           \_ /usr/lib/chromium/chromium --type=renderer --lang=en-
 9387 ?        Sl     0:01      |           \_ /usr/lib/chromium/chromium --type=renderer --lang=en- <--- this process is responsible
 9397 ?        Sl     0:00      |           \_ /usr/lib/chromium/chromium --type=renderer --lang=en-
 9402 ?        Sl     0:00      |           \_ /usr/lib/chromium/chromium --type=renderer --lang=en-
 9424 ?        Sl     0:00      |           \_ /usr/lib/chromium/chromium --type=renderer --lang=en-
 9554 ?        Sl     0:13      |           \_ /usr/lib/chromium/chromium --type=renderer --lang=en-
 9561 ?        Sl     0:01      |           \_ /usr/lib/chromium/chromium --type=renderer --lang=en-
 9568 ?        Sl     0:00      |           \_ /usr/lib/chromium/chromium --type=renderer --lang=en-
 9572 ?        Sl     0:00      |           \_ /usr/lib/chromium/chromium --type=renderer --lang=en-
 9578 ?        Sl     0:00      |           \_ /usr/lib/chromium/chromium --type=renderer --lang=en-
 9583 ?        Sl     0:00      |           \_ /usr/lib/chromium/chromium --type=renderer --lang=en-
 9649 ?        Sl     0:00      |           \_ /usr/lib/chromium/chromium --type=renderer --lang=en-
 9664 ?        Sl     0:01      |           \_ /usr/lib/chromium/chromium --type=renderer --lang=en-
 9675 ?        Sl     0:03      |           \_ /usr/lib/chromium/chromium --type=renderer --lang=en-
 9368 ?        Sl     0:08      \_ /usr/lib/chromium/chromium --type=gpu-process --channel=9321.0.12
 9391 ?        S      0:00          \_ /usr/lib/chromium/chromium --type=gpu-broker                 
----

Hi Alex, 

Thanks for your comment!

> and finding I am getting a baseline 100hz wakeup

Is this a lot or little?

Warmly,

~Robert

Sort of a lot, as in the new upcoming world magical world of 'Connected Standby'/InstantGo' this just stops the system being able to snooze into a lower power state.  The outcome is that my laptop battery drains at twice the rate as it does with Chromium not running.

I guess I could put chromium in a freezer cgroup, however it kind of kills the browsing experience some what :)

So the gripe is that whilst Chromium is not doing anything, everything is idle and I am on another virtual desktop not using it, it still prevents my laptop dropping into a lower power state.

Would be perfect if it throttled back on the wakeups when not doing anything.

Make sense?

Looking through the other bugs reported, is the SCTP malarkey linked to WebRTC?  If so, it maybe is an easy opportunity to only make this timer fire when those APIs are being exercised?

Cheers

Unable to repro this issue on Ubuntu Trusty (14.04) for Chromium Version - 51.0.2704.79

Screen-shot is attached.

@orschiro: Could you please perform the steps mentioned beneath and let us know your observations.

1. Update your Chromium - 51.0.2704.79
2. Re-test the same on a clean profile [chrome://settings -> Add Person]

@MTV: Tested this on Ubuntu Trusty [14.04], details beneath:

Memory - 15.4 GiB
Processor - Intel i7 - 4790 CPU@3.60Hz x 8
OS Type - 64 Bit
Graphis - Quadro K620/PCle/SSE2

Since the issue was reported on Linux laptop. Could you please look into this issue.

Thank you.

Dear @rnimmagadda,

Thank you your guidance!

Indeed, I am not sure what might have changed but process use decreased significantly. 

See attached file. 

~Robert

Deleted: task-manager.png 52.2 KB

	task-manager.png 52.2 KB View Download

CPU time != wakeups

The later you see in 'powertop', and though the computer might be idling (<1% CPU usage) the CPU will be unable to drop into a power saving mode as it is being woken up too often.

Still seeing the problem on Chromium 51.0.2704.79.  Both Vivaldi (1.3.544.25-1, based on Chromium 52) and Opera (38.0.2220.41 based on Chromium 51) do *not* have this problem.

Thank you for providing more feedback. Adding requester "rnimmagadda@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot