ERROR:sync_control_vsync_provider.cc(64)] : glXGetSyncValuesOML should not return TRUE with a media stream counter of 0.
Reported by
sirr...@hotmail.com,
Oct 9 2017
|
||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/61.0.3163.100 Chrome/61.0.3163.100 Safari/537.36 Steps to reproduce the problem: 1. open chrome/chromium and open several TAB-pages; 2. put the system in standby (s3 state) or let it to suspend; 3. resume from suspend to ram after several minutes. What is the expected behavior? to fix the issue; What went wrong? Chromium issues the following problem of syncing after resuming from S3 SUSPEND TO RAM, communicating the following LOG MESSAGE: [16620:16620:1009/123757.731687:ERROR:sync_control_vsync_provider.cc(64)] : glXGetSyncValuesOML should not return TRUE with a media stream counter of 0. Did this work before? N/A Chrome version: 61.0.3163.100 Channel: stable OS Version: 17.04/4.10 Flash Version:
,
Oct 9 2017
,
Oct 11 2017
looks like rendering or media issue.
,
Oct 31 2017
Dale, is this a media issue? [16620:16620:1009/123757.731687:ERROR:sync_control_vsync_provider.cc(64)] : glXGetSyncValuesOML should not return TRUE with a media stream counter of 0.
,
Oct 31 2017
,
Nov 3 2017
This LOG(ERROR) was changed by djkurtz in https://chromium.googlesource.com/chromium/src/+/e81d4aaa5fb68d8c22dc07cd6022003eafed11b8 It was added by backer in https://codereview.chromium.org/13871015, reviewed by marcheu. It sounds like this is the driver misbehaving and we're just logging it, which isn't problematic necessarily. Is this wontfix or anything to do marcheu?
,
Nov 3 2017
It's something we added to debug drivers for Chrome OS, where we could fix our drivers to match the spec. Now chrome OS doesn't use GLX any longer, and this is still there and triggering on Linux. The problem is that nowadays, when monitors go to sleep/suspend, the value drops to 0. That's become the de-facto spec at this point; I would say we can drop the error.
,
Jan 23 2018
assigning back to Dana, since I don't work on linux Chrome and I replied above to explain what's going on...
,
Jan 23 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/e70e2872be3a7cbee94d3547f33071f6c8ba20df commit e70e2872be3a7cbee94d3547f33071f6c8ba20df Author: danakj <danakj@chromium.org> Date: Tue Jan 23 20:44:35 2018 Remove the log message for media stream counter being 0. When glXGetSyncValuesOML is true, we expected this counter to be non-0 and added this error to find bugs, but it has become standard behaviour so this log is only generating noise. R=kbr@chromium.org Bug: 772844 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 Change-Id: I38377c74d45197cf33b2caf3cf81239075f8cae8 Reviewed-on: https://chromium-review.googlesource.com/881285 Reviewed-by: Kenneth Russell <kbr@chromium.org> Commit-Queue: danakj <danakj@chromium.org> Cr-Commit-Position: refs/heads/master@{#531340} [modify] https://crrev.com/e70e2872be3a7cbee94d3547f33071f6c8ba20df/ui/gl/sync_control_vsync_provider.cc
,
Jan 23 2018
|
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by sirr...@hotmail.com
, Oct 9 2017125 KB
125 KB View Download