From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 102358] WarThunder freezes at start, with activated vsync (vblank_mode=2)
Date: Wed, 23 Aug 2017 18:02:31 +0000 [thread overview]
Message-ID: <bug-102358-502-n054D3Ld28@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-102358-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 447 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=102358
--- Comment #5 from Thomas Hellström <thellstrom@vmware.com> ---
This looks odd.
That commit actually only adds a wait for all swaps to be scheduled at
glFinish(), so it shouldn't really be causing any grief unless the server
somehow forgets to send the right events or the dri3 wait_for_sbc is broken...
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1269 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 prev parent reply other threads:[~2017-08-23 18:02 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-22 11:40 [Bug 102358] WarThunder freezes always with vblanc=1 bugzilla-daemon
2017-08-22 18:12 ` [Bug 102358] WarThunder freezes always with vblank_mode=2 bugzilla-daemon
2017-08-22 18:14 ` [Bug 102358] WarThunder freezes at start, with activated vsync (vblank_mode=2) bugzilla-daemon
2017-08-23 2:04 ` bugzilla-daemon
2017-08-23 15:00 ` bugzilla-daemon
2017-08-23 15:32 ` bugzilla-daemon
2017-08-23 17:51 ` bugzilla-daemon
2017-08-23 18:02 ` bugzilla-daemon [this message]
2017-08-23 19:18 ` bugzilla-daemon
2017-08-25 11:23 ` bugzilla-daemon
2017-08-25 12:58 ` bugzilla-daemon
2017-08-25 14:36 ` bugzilla-daemon
2017-08-25 14:36 ` bugzilla-daemon
2017-08-25 16:18 ` bugzilla-daemon
2017-08-25 17:01 ` bugzilla-daemon
2017-08-25 17:35 ` bugzilla-daemon
2017-08-26 5:09 ` bugzilla-daemon
2017-08-26 16:03 ` bugzilla-daemon
2017-08-28 1:37 ` bugzilla-daemon
2017-08-28 12:08 ` bugzilla-daemon
2017-09-07 10:17 ` bugzilla-daemon
2017-09-07 14:34 ` bugzilla-daemon
2017-09-08 14:53 ` bugzilla-daemon
2017-09-17 17:43 ` bugzilla-daemon
2017-09-17 18:27 ` bugzilla-daemon
2017-09-19 18:00 ` bugzilla-daemon
2017-09-19 21:15 ` bugzilla-daemon
2017-09-19 21:32 ` bugzilla-daemon
2017-09-20 18:23 ` bugzilla-daemon
2017-10-18 21:53 ` bugzilla-daemon
2017-10-31 9:39 ` bugzilla-daemon
2017-11-02 10:50 ` bugzilla-daemon
2017-11-02 16:35 ` bugzilla-daemon
2017-11-02 16:41 ` bugzilla-daemon
2017-11-02 20:40 ` bugzilla-daemon
2017-11-03 14:02 ` bugzilla-daemon
2017-11-03 19:56 ` bugzilla-daemon
2017-11-03 20:40 ` bugzilla-daemon
2017-11-05 16:33 ` bugzilla-daemon
2017-11-05 17:30 ` bugzilla-daemon
2017-11-06 16:08 ` bugzilla-daemon
2017-11-13 13:14 ` bugzilla-daemon
2017-11-14 14:58 ` 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-102358-502-n054D3Ld28@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).