https://bugs.freedesktop.org/show_bug.cgi?id=88354
Bug ID: 88354
Summary: glXSwapBuffers() can cause BadMatch or lock X when
performed repeatedly
Product: Mesa
Version: 10.4
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: GLX
Assignee: mesa-dev@lists.freedesktop.org
Reporter: leftmost...@gmail.com
Created attachment 112152
--> https://bugs.freedesktop.org/attachment.cgi?id=112152&action=edit
Test program demonstrating crash/lock
When running a simple program to test window and GL context creation, I
experience program crashes or X lockups when the main loop calls
glXSwapBuffers() too rapidly. When the swap interval is not set, this appears
to always cause X to lock, with only the mouse responding. (n.b. When
attempting to drag windows, the cursor changes appropriately but the windows do
not respond.) If glXSwapIntervalMESA(1) is called, this occasionally merely
results in a program crash after some number of loops. In both cases, the
following error appears in the output and the program stops execution:
X Error of failed request: BadMatch (invalid parameter attributes)
Major opcode of failed request: 147 ()
Minor opcode of failed request: 1
Serial number of failed request: 163
Current serial number in output stream: 1034
After the end of execution, if X is locked, it remains locked until restarted.
Putting a one second delay into the main loop prevents the crash and programs
using GLX while rendering real results have not yet elicited any crashes,
suggesting this is a race condition somewhere. The test program I am using to
reproduce this is attached.
I am using mesa 10.4.1 with the i965 drivers on an Intel HD 3000 with kernel
3.17.8. All packages are from the Fedora 21 repositories.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev
