Revert of [Sensors] Reland: Align sensor reading updates and 'onchange' notification with rAF.

Revert of [Sensors] Reland: Align sensor reading updates and 'onchange' notification with rAF. (patchset #4 id:60001 of https://codereview.chromium.org/2589283003/ )

Reason for revert:
This looks like a likely cause of these failures: https://uberchromegw.corp.google.com/i/chromium.webkit/builders/WebKit%20Linux%20Trusty%20Leak/builds/945

Original issue's description:
> [Sensors] Reland: Align sensor reading updates and 'onchange' notification with rAF.
>
> For all sensors new reading values are read and 'onchange' notfication is send from rAF callbacks, thus avoiding possible Critical Rendering Path interruption.
>
> Before this change a timers were used and this could unnecessarily drain CPU and battery.
>
> BUG=668052
> BUG=606766
>
> Committed: https://crrev.com/6b071fe7dc3bd64a2914eadd5c67b483d064a6cb
> Cr-Commit-Position: refs/heads/master@{#439467}
>
> patch from issue 2551223003 at patchset 140001 (http://crrev.com/2551223003#ps140001)
>
> Committed: https://crrev.com/5f2cde61f6ff4a764b9b1c7d74a24ef6de815835
> Cr-Commit-Position: refs/heads/master@{#440208}

TBR=alexander.shalamov@intel.com,haraken@chromium.org,reillyg@chromium.org,mikhail.pozdnyakov@intel.com
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=668052
Committed: https://crrev.com/e2f7eddb1030e053847378b4202416c807fa298e
Cr-Commit-Position: refs/heads/master@{#440257}

[hcarmona, 2016-12-21 23:07:52]

The CQ bit was checked by hcarmona@chromium.org

[hcarmona, 2016-12-21 23:07:53]

Created Revert of [Sensors] Reland: Align sensor reading updates and 'onchange'
notification with rAF.

[commit-bot: I haz the power, 2016-12-21 23:08:21]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-12-21 23:09:09]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1482361672660480, "parent_rev":
"2158182686151023a5e7c7fe1b96f93f54774a74", "commit_rev":
"6dce610161dc27d1fc0fd2cddd7a47558f5c7bc9"}

[commit-bot: I haz the power, 2016-12-21 23:09:41]

Description was changed from

==========
Revert of [Sensors] Reland: Align sensor reading updates and 'onchange'
notification with rAF. (patchset #4 id:60001 of
https://codereview.chromium.org/2589283003/ )

Reason for revert:
This looks like a likely cause of these failures:
https://uberchromegw.corp.google.com/i/chromium.webkit/builders/WebKit%20Linu...

Original issue's description:
> [Sensors] Reland: Align sensor reading updates and 'onchange' notification
with rAF.
> 
> For all sensors new reading values are read and 'onchange' notfication is send
from rAF callbacks, thus avoiding possible Critical Rendering Path interruption.
> 
> Before this change a timers were used and this could unnecessarily drain CPU
and battery.
> 
> BUG=668052
> BUG=606766
> 
> Committed: https://crrev.com/6b071fe7dc3bd64a2914eadd5c67b483d064a6cb
> Cr-Commit-Position: refs/heads/master@{#439467}
> 
> patch from issue 2551223003 at patchset 140001
(http://crrev.com/2551223003#ps140001)
> 
> Committed: https://crrev.com/5f2cde61f6ff4a764b9b1c7d74a24ef6de815835
> Cr-Commit-Position: refs/heads/master@{#440208}

TBR=alexander.shalamov@intel.com,haraken@chromium.org,reillyg@chromium.org,mi...
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=668052
==========

to

==========
Revert of [Sensors] Reland: Align sensor reading updates and 'onchange'
notification with rAF. (patchset #4 id:60001 of
https://codereview.chromium.org/2589283003/ )

Reason for revert:
This looks like a likely cause of these failures:
https://uberchromegw.corp.google.com/i/chromium.webkit/builders/WebKit%20Linu...

Original issue's description:
> [Sensors] Reland: Align sensor reading updates and 'onchange' notification
with rAF.
> 
> For all sensors new reading values are read and 'onchange' notfication is send
from rAF callbacks, thus avoiding possible Critical Rendering Path interruption.
> 
> Before this change a timers were used and this could unnecessarily drain CPU
and battery.
> 
> BUG=668052
> BUG=606766
> 
> Committed: https://crrev.com/6b071fe7dc3bd64a2914eadd5c67b483d064a6cb
> Cr-Commit-Position: refs/heads/master@{#439467}
> 
> patch from issue 2551223003 at patchset 140001
(http://crrev.com/2551223003#ps140001)
> 
> Committed: https://crrev.com/5f2cde61f6ff4a764b9b1c7d74a24ef6de815835
> Cr-Commit-Position: refs/heads/master@{#440208}

TBR=alexander.shalamov@intel.com,haraken@chromium.org,reillyg@chromium.org,mi...
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=668052

Review-Url: https://codereview.chromium.org/2596063003
==========

[commit-bot: I haz the power, 2016-12-21 23:09:42]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-12-21 23:14:19]

Description was changed from

==========
Revert of [Sensors] Reland: Align sensor reading updates and 'onchange'
notification with rAF. (patchset #4 id:60001 of
https://codereview.chromium.org/2589283003/ )

Reason for revert:
This looks like a likely cause of these failures:
https://uberchromegw.corp.google.com/i/chromium.webkit/builders/WebKit%20Linu...

Original issue's description:
> [Sensors] Reland: Align sensor reading updates and 'onchange' notification
with rAF.
> 
> For all sensors new reading values are read and 'onchange' notfication is send
from rAF callbacks, thus avoiding possible Critical Rendering Path interruption.
> 
> Before this change a timers were used and this could unnecessarily drain CPU
and battery.
> 
> BUG=668052
> BUG=606766
> 
> Committed: https://crrev.com/6b071fe7dc3bd64a2914eadd5c67b483d064a6cb
> Cr-Commit-Position: refs/heads/master@{#439467}
> 
> patch from issue 2551223003 at patchset 140001
(http://crrev.com/2551223003#ps140001)
> 
> Committed: https://crrev.com/5f2cde61f6ff4a764b9b1c7d74a24ef6de815835
> Cr-Commit-Position: refs/heads/master@{#440208}

TBR=alexander.shalamov@intel.com,haraken@chromium.org,reillyg@chromium.org,mi...
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=668052

Review-Url: https://codereview.chromium.org/2596063003
==========

to

==========
Revert of [Sensors] Reland: Align sensor reading updates and 'onchange'
notification with rAF. (patchset #4 id:60001 of
https://codereview.chromium.org/2589283003/ )

Reason for revert:
This looks like a likely cause of these failures:
https://uberchromegw.corp.google.com/i/chromium.webkit/builders/WebKit%20Linu...

Original issue's description:
> [Sensors] Reland: Align sensor reading updates and 'onchange' notification
with rAF.
>
> For all sensors new reading values are read and 'onchange' notfication is send
from rAF callbacks, thus avoiding possible Critical Rendering Path interruption.
>
> Before this change a timers were used and this could unnecessarily drain CPU
and battery.
>
> BUG=668052
> BUG=606766
>
> Committed: https://crrev.com/6b071fe7dc3bd64a2914eadd5c67b483d064a6cb
> Cr-Commit-Position: refs/heads/master@{#439467}
>
> patch from issue 2551223003 at patchset 140001
(http://crrev.com/2551223003#ps140001)
>
> Committed: https://crrev.com/5f2cde61f6ff4a764b9b1c7d74a24ef6de815835
> Cr-Commit-Position: refs/heads/master@{#440208}

TBR=alexander.shalamov@intel.com,haraken@chromium.org,reillyg@chromium.org,mi...
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=668052

Committed: https://crrev.com/e2f7eddb1030e053847378b4202416c807fa298e
Cr-Commit-Position: refs/heads/master@{#440257}
==========

[commit-bot: I haz the power, 2016-12-21 23:14:20]

Patchset 1 (id:??) landed as
https://crrev.com/e2f7eddb1030e053847378b4202416c807fa298e
Cr-Commit-Position: refs/heads/master@{#440257}

[haraken, 2016-12-22 00:23:16]

LGTM

[Mikhail, 2016-12-22 10:07:27]

The given https://uberchromegw.corp.google.com is not available for
non-googlers. Could I know somehow what were the problems there with the
reverted cl?

[hcarmona, 2016-12-22 18:09:08]

On 2016/12/22 10:07:27, Mikhail wrote:
> The given https://uberchromegw.corp.google.com is not available for
> non-googlers. Could I know somehow what were the problems there with the
> reverted cl?

Sorry, did not realize URL was not accessible.

The failures are in webkit_tests

Regressions: Unexpected crashes (4)
  sensor/accelerometer.html [ Crash ]
  sensor/ambient-light-sensor.html [ Crash ]
  sensor/gyroscope.html [ Crash ]
  sensor/magnetometer.html [ Crash ]