Fix a CHECK when monitor configuration changes

Fix a CHECK when monitor configuration changes

This fix is specific to GPU V-sync configuration (e.g. running
Chrome with --enable-features=D3DVsync switch).

When monitor configuration changes GetMonitorInfo returns FALSE and
the output data remains uninitialized. In this case GpuVSyncProvider
will use a backup delay based v-sync mechanism.

It looks a similar problem might exist in a general case as well.
I am going to address it separately.

BUG=467617
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel

Review-Url: https://codereview.chromium.org/2846613002
Cr-Commit-Position: refs/heads/master@{#467504}
Committed: https://chromium.googlesource.com/chromium/src/+/d476ca3a02a6c06d45ef3d83573fa094ca4f52d7

[stanisc, 2017-04-26 22:00:53]

Description was changed from

==========
Fix a CHECK when a monitor configuration changes

BUG=
==========

to

==========
Fix a CHECK when a monitor configuration changes

BUG=
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
==========

[stanisc, 2017-04-26 22:01:08]

The CQ bit was checked by stanisc@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-04-26 22:02:03]

Dry run: CQ is trying da patch.

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

[stanisc, 2017-04-26 22:09:15]

Description was changed from

==========
Fix a CHECK when a monitor configuration changes

BUG=
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
==========

to

==========
Fix a CHECK when monitor configuration changes

This fix is specific to GPU V-sync configuration (e.g. running
Chrome with --enable-features=D3DVsync switch).

When monitor configuration changes GetMonitorInfo returns FALSE and
the output data remains uninitialized. In this case GpuVSyncProvider
will use a backup delay based v-sync mechanism.

It looks a similar problem might exist in a general case as well.
I am going to address it separately.

BUG=467617
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
==========

[stanisc, 2017-04-26 22:09:15]

stanisc@chromium.org changed reviewers:
+ jbauman@chromium.org

[stanisc, 2017-04-26 22:10:30]

PTAL!

[jbauman, 2017-04-26 22:24:41]

lgtm

[commit-bot: I haz the power, 2017-04-26 23:07:22]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-04-26 23:07:22]

Dry run: This issue passed the CQ dry run.

[stanisc, 2017-04-26 23:11:24]

The CQ bit was checked by stanisc@chromium.org

[commit-bot: I haz the power, 2017-04-26 23:12:01]

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, 2017-04-26 23:21:55]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1493248284159680, "parent_rev":
"db34acee25d2f2c141ded0b76645d81ffeb298d0", "commit_rev":
"d476ca3a02a6c06d45ef3d83573fa094ca4f52d7"}

[commit-bot: I haz the power, 2017-04-26 23:22:07]

Description was changed from

==========
Fix a CHECK when monitor configuration changes

This fix is specific to GPU V-sync configuration (e.g. running
Chrome with --enable-features=D3DVsync switch).

When monitor configuration changes GetMonitorInfo returns FALSE and
the output data remains uninitialized. In this case GpuVSyncProvider
will use a backup delay based v-sync mechanism.

It looks a similar problem might exist in a general case as well.
I am going to address it separately.

BUG=467617
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
==========

to

==========
Fix a CHECK when monitor configuration changes

This fix is specific to GPU V-sync configuration (e.g. running
Chrome with --enable-features=D3DVsync switch).

When monitor configuration changes GetMonitorInfo returns FALSE and
the output data remains uninitialized. In this case GpuVSyncProvider
will use a backup delay based v-sync mechanism.

It looks a similar problem might exist in a general case as well.
I am going to address it separately.

BUG=467617
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel

Review-Url: https://codereview.chromium.org/2846613002
Cr-Commit-Position: refs/heads/master@{#467504}
Committed:
https://chromium.googlesource.com/chromium/src/+/d476ca3a02a6c06d45ef3d83573f...
==========

[commit-bot: I haz the power, 2017-04-26 23:22:08]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/d476ca3a02a6c06d45ef3d83573f...