Bugzilla

(In reply to Jeff Gilbert [:jgilbert] from comment #21)
> "WebGL context was lost soon within 3 seconds" sounds like out context-loss timer triggering context-loss when it hits that non-zero value.
> One last thing I'd like to try is on `Adreno3xx && es2`, just treat 0x1 as 0x0.
> Can you try this locally?

I tried it. In this case, glGetGraphicsResetStatus() did not return other error than 0x0. Then WebGL context was lost by GLScreenBuffer::PublishFrame() failure that was caused by oom.

(In reply to Jeff Gilbert [:jgilbert] from comment #21)
> "WebGL context was lost soon within 3 seconds" sounds like out context-loss timer triggering context-loss when it hits that non-zero value.
> One last thing I'd like to try is on `Adreno3xx && es2`, just treat 0x1 as 0x0.
> Can you try this locally?

I tried it. In this case, glGetGraphicsResetStatus() did not return other error than 0x1. 0x1 was returned very often. Then WebGL context was lost by GLScreenBuffer::PublishFrame() failure that was caused by oom.