[Bug 103948] SIGSEGV when using 0 for YUV values

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu Feb 1 15:51:04 UTC 2018


pauldotknopf at gmail.com changed:

           What    |Removed                     |Added
             Status|NEEDINFO                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #6 from pauldotknopf at gmail.com ---
There was a race condition in my software. The buffer being sent was being
changed, in transit. Adding proper locks resolved the issue.

I'm guessing the mesa drivers work better/more efficiently with 0 values,
causing this race condition to happen.

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

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