https://bugs.freedesktop.org/show_bug.cgi?id=86651
Chris Wilson <ch...@chris-wilson.co.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|Driver/intel |GLX
Assignee|ch...@chris-wilson.co.uk |mesa-dev@lists.freedesktop.
| |org
Product|xorg |Mesa
QA Contact|intel-gfx-bugs@lists.freede |
|sktop.org |
--- Comment #2 from Chris Wilson <ch...@chris-wilson.co.uk> ---
Bisecting the server reveals:
commit d0da0e9c3bb8fe0cd4879ecb24d21715bfaa209b
Author: Eric Anholt <e...@anholt.net>
Date: Thu Sep 4 10:59:40 2014 -0700
glx: Disable indirect GLX contexts by default.
Almost every situation of someone running indirect GLX is a mistake
that results in X Server crashes. Indirect GLX is the cause of
regular security vulnerabilities, and rarely provides any capability
to the user. Just disable it unless someone wants to enable it for
their special use case (using +iglx on the command line).
Signed-off-by: Eric Anholt <e...@anholt.net>
Acked-by: Keith Packard <kei...@keithp.com>
Signed-off-by: Keith Packard <kei...@keithp.com>
So the question is why is mesa creating an indirect context in this case?
--
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
