Re: [Public WebGL] OUT_OF_MEMORY error in 1.0.1/conformance/reading/read-pixels-test

[Gregg Tavares <gman@google.com>]

IIRC the tests have been written to use a reasonable (less than 60meg) amount of memory.

The spec unfortunately makes it possible for every function to generate GL_OUT_OF_MEMORY period and still be technically spec compliant.

In other words, according to the spec an implementation could to this

GLenum glGetErrror() { return GL_OUT_OF_MEMORY; }

void glBindBuffer(...) { /* no-op */ }

void glBindTexture(...) { /* no-op */ }

void glTexImage2D(...) { /* no-op */ }

void glDrawArrays(...) { /* no-op */ }

And be valid according to the spec :-(

On Wed, Apr 3, 2013 at 12:25 AM, Jeff Gilbert <jgilbert@mozilla.com> wrote:

On some mobile devices, we're hitting a couple errors followed by a gl.OUT_OF_MEMORY error in the "check reading with lots of drawing" section. This is AFAIK spec-compliant behavior, so I believe the test should be changed to gl.flush() after each draw call, which seems to have fixed it for me.

Thoughts?

-Jeff

-----------------------------------------------------------
You are currently subscribed to public_webgl@khronos.org.
To unsubscribe, send an email to majordomo@khronos.org with
the following command in the body of your email:
unsubscribe public_webgl
-----------------------------------------------------------