GitLab

As per the spec, the driver is expected to return a valid timestamp from
the call eglGetFrameTimestampsANDROID() when its not
EGL_TIMESTAMP_PENDING_ANDROID or EGL_TIMESTAMP_INVALID_ANDROID.
But currently few buggy drivers returns an invalid timestamp 0.

We fix/workaround this in chrome by returning the presentation time
as TimeTicks::Now() (snapped to the next vsync) instead of 0.

Bug: 966638
Change-Id: I5075dda0739f02029922ebbc20c09656fb0e87ba
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1631354Reviewed-by: Antoine Labour <piman@chromium.org>
Commit-Queue: vikas soni <vikassoni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#663918}