To clarify, drivers never generate errors in such situation. It's
simply an undefined behavior. The error you see is not from NVidia
drivers, but from Chrome's GPU command buffer.
On Sun, Mar 19, 2017 at 2:07 PM, Florian Bösch <email@example.com> wrote:
> I might add, OpenGL adopts the latter more lenient interptation (at least
> with nvidia drivers), and that works fine on Chrome on these systems, but
> on Windows Chrome/ANGLE use a more strict interpretation.
> On Sun, Mar 19, 2017 at 10:05 PM, Florian Bösch <firstname.lastname@example.org> wrote:
>> The ES specification states that the result of sampling from a texture
>> attached to a framebuffer at the same time as sampling to that framebuffer
>> is undefined.
>> Google chrome seems to interprete this as: If a texture is bound to any
>> texturing unit while that framebuffer is used it's an error.
>> However a different interpretation of this would be: If a texture that is
>> bound is actually sampled during the framebuffer operation it's an error.
>> Which of these interpretations is the correct one?