Gldebug implements a mechanism for wrapping and monitoring all webGL calls
- Gldebug.start(opts) applies a wrapper to all gl and gl extension functions.
- Gldebug.stop() restores the original gl builtin functions.
Gldebug imposes a very significant overhead so should be used sparingly, but can be very helpful for debugging without the need to make code changes. Calls to Gldebug can be made from code, or from Dev Tools. One useful pattern is to add code that allows a clause in location.search to start Gldebug.
The wrapper can check for gl errors before (should be unnecessary) and after every gl call. The wrapper logs some statistics, and takes optional actions, depending on 'action' and any error found.
Gldebug has been coded for use with three.js, but should work for any WebGL application.
action is a string that can contain one or more of
- logall: all gl calls are logged
- logerr: gl error calls are logged
- breakall: debugger break on every gl call
- breakerr: debugger break on error gl calls
- checkbefore: checks are carried out before each call (by default they are not)
- nocheckafter: checks are not carried out after each call (by default they are)
Gldebug.start() takes an options object as input, which can contain
- gl: gl context, if not given this may be deduced from window.gl or Gldebug.gl
- action: action string as above: defaults to 'logerr'
- frames: number of frames to debug before automatic stop: defaults to Infinity.
- frameOwner: object in which the frame counter lives: defaults to window
- frameName: name of frame counter field within frameOwner: defaults to 'framenum'
It is the user program responsibility to update frameOwner[frameName]. Frame counting will depend on exactly where in the frame cycle the start call and framenum update happen.
As a shortcut Gldebug.start() may be called with an integer (frames) or a string (action)
Additionally: Gldebug.checkglerr() may be called at any point of a user program to check for outstanding gl errors and take appropriate action.
By default Gldebug logging and error messages are directed to the console;
these can be overridden by setting Gldebug.serious, Gldebug.showbaderror, Gldebug.error, and Gldebug.log
Gldebug.start()// check all gl calls and log errors, until stopGldebug.start(1)// check all gl calls for 1 frame and log errorsGldebug.start({gl, action: 'logall', frames: 1})// log all gl calls for 1 frameGldebug.stop()// stop Gldebug, remove all gl call wrappersGldebug.checkglerr('test')// explicit call to check current gl error status