Benoit Jacob
f17096872f
Bug 938489 - 2/3. Don't include GL headers in glxtest - r=karlt
2013-11-18 08:08:24 -05:00
Birunthan Mohanathas
bfeb1b105e
Bug 784739 - Switch from NULL to nullptr in toolkit/; r=ehsan
2013-10-10 16:36:42 -04:00
Benoit Jacob
1908a951bc
Bug 786383 - add MOZ_AVOID_OPENGL_ALTOGETHER option - r=karlt
2012-09-21 13:44:35 -04:00
Benoit Jacob
9948f9058a
Bug 680644 - Simplify glxtest and make it similar to glxinfo to avoid X server crashes - r=karlt
...
We were getting orange B's due to X server crashes on builders.
2012-08-28 15:38:08 -04:00
Martin Vogt
12e20f88a4
Bug 680644 - Let glxtest use a XWindow instead of a GLXPixmap - r=bjacob
...
This simplifies code and avoids a X server crash with certain FGLRX setups.
2012-08-22 23:16:30 -04:00
Gervase Markham
ca171eec44
Bug 716478 - update licence to MPL 2.
2012-05-21 12:12:37 +01:00
Matt Brubeck
58eb5eeac0
Back out c209fea124e1 (bug 754198) because of Win64 build failure
2012-05-11 13:23:49 -07:00
Fabrice Desré
8c0c24a4a2
Bug 754198 - Warning treated as error in jemalloc.c. Build busted. [r=jlebar,bsmedberg]
2012-05-11 12:34:24 -07:00
Benoit Jacob
b5c12a324e
Bug 719164 - Silence glxtest to get rid of spurious messages from the GL - r=glandium
2012-02-08 21:55:34 -05:00
Benoit Jacob
454c9e5c23
Bug 718629 - intermittent waitpid failure causes OpenGL features to be blacklisted on X11 - r=karlt
2012-01-31 15:32:05 -05:00
Nicholas Miell
2155a99955
Bug 715952 - glxtest incorrectly creates the backing pixmap and causes X errors - r=bjacob
...
Was always using 32bit depth, disregarding the actual depth of the FBConfig. This was causing a X error on Mesa sofware renderers.
2012-01-07 18:45:48 -05:00
Landry Breuil
d81b4a6adc
Bug 687320 - On OpenBSD, libGL.so.1 doesn't exist - r=bjacob
...
Opening libGL.so will work regardless of the version, which changes over time.
2011-10-25 08:48:39 -04:00
Benoit Jacob
d95a9a4e30
Bug 683500 - glxtest should use glXGetProcAddress, not dlsym - r=mattwoodrow
...
As discussed on https://bugs.freedesktop.org/show_bug.cgi?id=40423
2011-09-07 17:17:45 -04:00
Phil Ringnalda
946b02e238
Back out d333f4021aaf, 5e90688c720e and bdb0bff93ce8 for Windows build redness
2011-09-07 15:20:26 -07:00
Benoit Jacob
87e4ea0544
Bug 683500 - glxtest should use glXGetProcAddress, not dlsym - r=mattwoodrow
...
As discussed on https://bugs.freedesktop.org/show_bug.cgi?id=40423
2011-09-07 17:17:45 -04:00
Ginn Chen
f4562760b6
Bug 674468 glxtest.cpp fails to compile with Solaris Studio r=karlt
2011-08-30 13:27:19 +08:00
Benoit Jacob
581f9bb68c
Bug 659932 - GLXtest process should check for GLX >= 1.3 before calling glXCreatePixmap - r=dbaron
...
This gives cleaner error messages when trying to use GLX features on old GLXs.
2011-08-19 11:39:00 -04:00
Matt Woodrow
018085f85d
Bug 671259 - Disable OpenGL layers on linux when we don't have texture_from_pixmap. r=bjacob
2011-08-05 13:13:25 +12:00
Benoit Jacob
4285792db3
Bug 659842 comment 86 - accidentally removed a glXDestroyContext call + fix a warning in opt build - r=trivial-fix
2011-06-17 21:42:31 -04:00
Benoit Jacob
8dbe82a76f
Bug 659842 - [topcrash] release the GL context before calling glXDestroyContext - r=karlt
...
See the glXDestroyContext man page:
If GLX rendering context ctx is not current to any thread,
glXDestroyContext destroys it immediately. Otherwise, ctx is destroyed
when it becomes not current to any thread. In either case, the resource ID
referenced by ctx is freed immediately.
In other words, if we want glXDestroyContext to have the well-defined semantics
of destroying the context before future X commands take effect, we must first
release the GL context before calling it. We were failing to do that, but we
were destroying the drawable immediately after that call, and as a result, the
context was outliving its underlying drawable. This eventually resulted in
X_GLXMakeCurrent: GLXBadContextTag X errors on subsequent glXMakeCurrent calls.
2011-06-17 11:49:27 -04:00
Benoit Jacob
d18185a968
Bug 658840 - let glxtest process return from XRE_main rather than calling exit() - r=bsmedberg
...
Calling exit() resulted in two strings being considered leaked by valgrind. Returning from XRE_main() should fix that.
2011-06-10 15:07:54 -04:00
Benoit Jacob
90532908fc
Bug 660466 - segfault in glxtest - check if a visual was found - r=karlt
2011-06-10 15:05:10 -04:00
Benoit Jacob
956ce06d6e
Bug 660466 - segfault in glxtest - check if any fbconfig was found - r=karlt
2011-06-10 15:04:20 -04:00
Benoit Jacob
9bd5e2acc1
Bug 639842 - implement glxtest probe running as separate process - r=bsmedberg,joe
2011-05-03 16:07:17 -04:00
