DescriptionCHECK failure in gpu::GpuVSyncWorker::OpenAdapter and UMA for error codes
The previous fix (see crrev.com/2883683002) was insufficient. It looks
like there is at least one more possible error code returned from
OpenAdapter - STATUS_UNSUCCESSFUL. It should be better to just cover all
possible error codes and fallback to delay based v-sync for any reason.
Additionally, as discussed in CR for the previous fix, I've added an
UMA histogram for tracking how many GPU v-sync cycles end up failing for
one of 3 different reasons vs. the number of successful v-sync cycles.
BUG=721521
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/2901693002
Cr-Commit-Position: refs/heads/master@{#474406}
Committed: https://chromium.googlesource.com/chromium/src/+/c76c0fd5ab7540ba6d28ea16b0ad305b086d55c5
Patch Set 1 #
Total comments: 4
Patch Set 2 : Addressed CR feedback #
Total comments: 2
Patch Set 3 : Single entrypoint to UMA_HISTOGRAM_ENUMERATION #
Messages
Total messages: 25 (18 generated)
|