Benoit Jacob
ff87bf481b
Bug 938489 - 2/3. Don't include GL headers in glxtest - r=karlt
2013-11-18 08:08:24 -05:00
Birunthan Mohanathas
b2658eb131
Bug 784739 - Switch from NULL to nullptr in toolkit/; r=ehsan
2013-10-10 16:36:42 -04:00
Benoit Jacob
3321942c35
Bug 786383 - add MOZ_AVOID_OPENGL_ALTOGETHER option - r=karlt
2012-09-21 13:44:35 -04:00
Benoit Jacob
e5257b17de
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
a9cc8b6088
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
82ff7027aa
Bug 716478 - update licence to MPL 2.
2012-05-21 12:12:37 +01:00
Matt Brubeck
60b5d7f292
Back out c209fea124e1 (bug 754198) because of Win64 build failure
2012-05-11 13:23:49 -07:00
Fabrice Desré
5397f4846a
Bug 754198 - Warning treated as error in jemalloc.c. Build busted. [r=jlebar,bsmedberg]
2012-05-11 12:34:24 -07:00
Benoit Jacob
e6e23447b9
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
444c5c0219
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
06e71a8aa2
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
11ea4e2516
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
83dd849601
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
446a63d453
Back out d333f4021aaf, 5e90688c720e and bdb0bff93ce8 for Windows build redness
2011-09-07 15:20:26 -07:00
Benoit Jacob
9c1c275870
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
67d155be54
Bug 674468 glxtest.cpp fails to compile with Solaris Studio r=karlt
2011-08-30 13:27:19 +08:00
Benoit Jacob
2a4987ad1d
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
bf397acbd6
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
1727f110cb
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
4500b8e8dc
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
52a0dd4eeb
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
74758ffbcb
Bug 660466 - segfault in glxtest - check if a visual was found - r=karlt
2011-06-10 15:05:10 -04:00
Benoit Jacob
0123ed0bf8
Bug 660466 - segfault in glxtest - check if any fbconfig was found - r=karlt
2011-06-10 15:04:20 -04:00
Benoit Jacob
5728b278e4
Bug 639842 - implement glxtest probe running as separate process - r=bsmedberg,joe
2011-05-03 16:07:17 -04:00