[Mesa-dev] [Bug 98833] [REGRESSION, bisected] Wayland revert commit breaks fullscreen frame updates

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu Nov 24 10:09:01 UTC 2016


https://bugs.freedesktop.org/show_bug.cgi?id=98833

--- Comment #4 from Pekka Paalanen <ppaalanen at gmail.com> ---
> (In reply to Pekka Paalanen from comment #2)
> > (In reply to Eero Tamminen from comment #0)
> > > Test suite has options for using single, double or triple buffering and
> > > toggling Vsync, but these didn't have any effect.
> [...]
> > I could understand better if you explained what you use in EGL API terms
> > instead, since AFAIK there is no way to explicitly choose a "buffering
> > scheme", EGL made sure to abstract that away from the app.
> 
> They were just options in the test-suite, I'll check whether they actually
> should do something on EGL/Wayland (test-suite supports also other APIs & 
> OSes, so it's possible that all options aren't supported on all platforms).
> 
> 
> Apitrace replay didn't work on a trace, do I need to do something specific
> to get Apitrace to replay traces on Wayland?
> 
> (Apitrace changes some things, so I don't trust trace dump to be reliable in
> telling how program works until I've seen issue also on trace replay.)

Sorry, no idea about apitrace.

Since it's a buffer posting issue instead of a rendering issue, I thought it
might be fairly easy to write a minimal program reproducing the problem if we
knew how your test suite uses EGL. It shouldn't matter at all which flavour of
GL was used, except for portability. I'm not aware of an existing test program
like that, so Weston repository could probably use one similar to
presentation-shm which can run in one of several different operating modes and
report timings.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/mesa-dev/attachments/20161124/47006726/attachment.html>


More information about the mesa-dev mailing list