We're seeing yet another crash because of wrong context bug in GL. Now that we ...
13 years, 2 months ago
(2011-08-31 15:25:01 UTC)
#1
We're seeing yet another crash because of wrong context bug in GL.
Now that we are able to specify a GrGLInterface per-GrContext we're in position
to have a callback that can be used to set the correct context. I won't check
this in until I've made sure it'll work in Chrome.
http://codereview.appspot.com/4964055/diff/1/gpu/include/GrGLConfig.h
File gpu/include/GrGLConfig.h (right):
http://codereview.appspot.com/4964055/diff/1/gpu/include/GrGLConfig.h#newcode207
gpu/include/GrGLConfig.h:207: (IFACE)->f##X;
\
We were relying on the fact that this line began the macro implementation in
order to make return values from gl funcs work. e.g.
GrGLenum status = GR_GL_CALL(gl, CheckFramebufferStatus(...));
Now the callback comes first. So I made new versions of the macros for capturing
the return value.
LGTM. Just a few nits and an observation. http://codereview.appspot.com/4964055/diff/3001/gpu/src/GrGLProgram.cpp File gpu/src/GrGLProgram.cpp (right): http://codereview.appspot.com/4964055/diff/3001/gpu/src/GrGLProgram.cpp#newcode895 gpu/src/GrGLProgram.cpp:895: GetUniformLocation(progID, ...
13 years, 2 months ago
(2011-08-31 20:34:15 UTC)
#2
Issue 4964055: Optional per-gl-cmd callback in GrGLInterface
(Closed)
Created 13 years, 2 months ago by bsalomon
Modified 13 years, 2 months ago
Reviewers: twiz, reed1
Base URL: http://skia.googlecode.com/svn/trunk/
Comments: 7