From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 98964] Chromium complains about glXGetSyncValuesOML in 13.0.2
Date: Fri, 02 Dec 2016 09:31:09 +0000 [thread overview]
Message-ID: <bug-98964-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 902 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=98964
Bug ID: 98964
Summary: Chromium complains about glXGetSyncValuesOML in 13.0.2
Product: Mesa
Version: 13.0
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: zboszor@pr.hu
QA Contact: dri-devel@lists.freedesktop.org
Hi,
I am running Chromium 52.0.2743.76 on Yocto with Mesa 13.0.2 / libdrm 2.4.73.
It occasionally complains about this:
[1347:1347:1202/032132:ERROR:sync_control_vsync_provider.cc(64)]
glXGetSyncValuesOML should not return TRUE with a media stream counter of 0.
Conformance bug?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2281 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2016-12-02 9:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 9:31 bugzilla-daemon [this message]
2016-12-02 9:32 ` [Bug 98964] Chromium complains about glXGetSyncValuesOML in 13.0.2 bugzilla-daemon
2016-12-02 19:40 ` bugzilla-daemon
2016-12-03 5:47 ` bugzilla-daemon
2016-12-05 21:58 ` bugzilla-daemon
2016-12-05 22:00 ` bugzilla-daemon
2016-12-06 5:18 ` bugzilla-daemon
2016-12-06 5:39 ` bugzilla-daemon
2016-12-06 12:02 ` bugzilla-daemon
2016-12-06 12:38 ` bugzilla-daemon
2016-12-06 13:20 ` bugzilla-daemon
2016-12-06 14:45 ` bugzilla-daemon
2019-09-18 19:40 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-98964-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).