Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(20)

Issue 10833030: Prevent multile DoPoll() calls from being simultaneously pending (Closed)

Created:
8 years, 5 months ago by jar (doing other things)
Modified:
8 years, 5 months ago
Reviewers:
scottmg
CC:
chromium-reviews, joi+watch-content_chromium.org, darin-cc_chromium.org, jam
Visibility:
Public.

Description

Prevent multile DoPoll() calls from being simultaneously pending r=scottmg BUG=139084 Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=148631

Patch Set 1 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+12 lines, -0 lines) Patch
M content/browser/gamepad/gamepad_provider.h View 1 chunk +5 lines, -0 lines 0 comments Download
M content/browser/gamepad/gamepad_provider.cc View 4 chunks +7 lines, -0 lines 0 comments Download

Messages

Total messages: 4 (0 generated)
jar (doing other things)
8 years, 5 months ago (2012-07-26 03:23:43 UTC) #1
scottmg
lgtm Note that the delay is 16ms, so it ought to be on the order ...
8 years, 5 months ago (2012-07-26 16:02:08 UTC) #2
jar (doing other things)
<oops> my mistake. I spotted chrome/src/content/browser/device_orientation/provider_impl.h which also had a kDesiredSamplingIntervalMs. You are correct... it ...
8 years, 5 months ago (2012-07-26 22:13:58 UTC) #3
scottmg
8 years, 5 months ago (2012-07-26 22:25:26 UTC) #4
On 2012/07/26 22:13:58, jar wrote:
> <oops>  my mistake.  I spotted
> chrome/src/content/browser/device_orientation/provider_impl.h
> which also had a kDesiredSamplingIntervalMs.
> 
> You are correct... it is supposed to be 16ms, when I look in the "right" file:
> 
> chrome/src/content/browser/gamepad/gamepad_provider.h

Ah, perhaps we should rename that kDesiredGamepadSamplingIntervalMs to be more
clear.

> 
> Sorry about my confusion.
> 
> 
> On 2012/07/26 16:02:08, scottmg wrote:
> > lgtm
> > 
> > Note that the delay is 16ms, so it ought to be on the order of 60/second
when
> > running, not 10 (per bug).

Powered by Google App Engine
This is Rietveld 408576698