Steps to reproduce the problem:
The user-agent of the failing device:  Mozilla/5.0 (Linux; Android 4.4.2; SAMSUNG-SGH-I747 Build/KOT49H) AppleW
ebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.68 Mobile Safari/537.36

1.  Load crash.html on a Samsung Galaxy S3 (SAMSUNG-SGH-I747)
2.  Wait approximately five seconds
3.  Notice that the GL context has been lost.  The blue canvas disappears.

When attaching to the console over USB, I see there are GL errors in the console log.  Note that there are many (C level) gl API calls reporting errors, where my test case is merely repeatedly clearing the render target, and nothing more.  The following is pasted from the console:

3crash.html:1 [.Offscreen-For-WebGL-0x633e5040]GL ERROR :GL_INVALID_ENUM : glTexImage2D: <- error from previous GL command
4crash.html:1 [.Offscreen-For-WebGL-0x633e5040]GL ERROR :GL_INVALID_ENUM : glFramebufferTexture2DMultisample: <- error from previous GL command
crash.html:1 [.Offscreen-For-WebGL-0x633e5040]GL ERROR :GL_INVALID_ENUM : glTexImage2D: <- error from previous GL command
6crash.html:1 [.Offscreen-For-WebGL-0x633e5040]GL ERROR :GL_INVALID_ENUM : glFramebufferTexture2DMultisample: <- error from previous GL command
crash.html:1 [.Offscreen-For-WebGL-0x633e5040]GL ERROR :GL_INVALID_ENUM : glTexImage2D: <- error from previous GL command
2crash.html:1 [.Offscreen-For-WebGL-0x633e5040]GL ERROR :GL_INVALID_ENUM : glFramebufferTexture2DMultisample: <- error from previous GL command
crash.html:1 GL_INVALID_OPERATION : glGenSyncTokenCHROMIUM: fence sync must be flushed before generating sync token
crash.html:1 WebGL: CONTEXT_LOST_WEBGL: loseContext: context lost

What is the expected behavior?
No lost GL context.  The blue canvas should remain visible indefinitely.

What went wrong?
"Rats!  WebGL hit a snag."  The GL context was lost.  

Attached is the output of "chrome://gpu" on the device.

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 54.0.2840.68  Channel: stable
OS Version: Android 4.4.2
Flash Version: 

The attached test case works as expected when loaded in Chrome on my desktop.  It also works as expected when loaded in Firefox on the same Galaxy S3 device where it fails in Chrome.
 

Deleted: crash.html 419 bytes

crash.html 419 bytes View Download

Deleted: s3-gpu.html.gz 18.6 KB

s3-gpu.html.gz 18.6 KB Download