For security reasons, Chrome validates many GL operations that other drivers may not. It's a bit of work, but you might try searching the Chromium codebase using http://cs.chromium.org to find the error messages.
Here's what I found:
BackTexture::AllocateStorage: <- error from previous GL command
This one is tricky to follow. As it says, some previous GL command failed before
BackTexture::AllocateStorage
was called. I looked through the rest of the file, and it's not clear to me what command is failing here, but from the error value it is framebuffer related.glVertexAttribPointer: stride not valid for type and glVertexAttribPointer: offset not valid for type
These are pretty clear -- the stride and offset values are not divisible by the component size. It would be useful to see your calls to
glVertexAttribPointer
.glDrawElements: attempt to access out of range vertices in attribute 0
VertexAttrib::CanAccess
is failing, which checks whether the attrib is enabled, not deleted, and if the vertex index that you're trying to access is valid. As the error says, you are likely referencing a vertex outside of the valid range.
To debug this, I'd narrow down the calls to glDrawElements
and glVertexAttribPointer
and try to find which one is failing, then I'd add some printf
calls to see what values are being passed.
Good luck!