[Bug 99507] Corrupted frame contents for Sascha Willems' demos when they're run Vsynched in fullscreen

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Jan 23 15:20:44 UTC 2017


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

            Bug ID: 99507
           Summary: Corrupted frame contents for Sascha Willems' demos
                    when they're run Vsynched in fullscreen
           Product: Mesa
           Version: git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/DRI/i965
          Assignee: intel-3d-bugs at lists.freedesktop.org
          Reporter: eero.t.tamminen at intel.com
        QA Contact: intel-3d-bugs at lists.freedesktop.org

Created attachment 129109
  --> https://bugs.freedesktop.org/attachment.cgi?id=129109&action=edit
Photo of the problem

Sacha Willem's demos:
  https://github.com/SaschaWillems/Vulkan

Just got support for running in fullscreen, at monitor's native resolution:
  https://github.com/SaschaWillems/Vulkan/issues/268

However, at least with Ubuntu 16.04 on SKL GT2,with latest git versions of
Vulkan loader & Mesa, frame content is slightly corrupted when tests are
running Vsynched, for example:
  ./raytracing -fullscreen -vsync

(By default the demos are currently vsynched in fullscreen, but it may change,
hence the use of -vsync option.)

When I tried running the demos without Vsync (= no "-vsync" option, MAILBOX
mode commented out from vulkanswapchain.hpp), i.e. X server will make a copy of
the frame content to screen, output looks fine.  Screenshots (=copy of the
frame)  also look fine.

I don't see it in all demos, but that could be a fluke.  It was visible at
least in these:
- computecullandlod (very faintly)
- computenbody (very clearly)
- dynamic uniform buffers
- gears (occasionally)
- geometryshader
- indirectdraw
- multithreading
- particlefire (in fire)
- pushconstants
- raytracing (compute shader)
- specializationconstants
- texture
- texture3d
- texturearray
- texturecubemap (very faintly)
- texturemipmapgen (very faintly)

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20170123/0a43c1b7/attachment.html>


More information about the intel-3d-bugs mailing list