This seems to be working fine on Mac OS 10.12.5 on canary version:61.0.3143.0 and is Linux specific.

You are probably looking for a change made after 438878 (known good), but no later than 438885 (first known bad).
CHANGELOG URL:
  https://chromium.googlesource.com/chromium/src/+log/e63ccacfa0b3e8bfcfa0f5c7e64239c881a20861..f615b0af7fea1d9dfb86e33a036ca08252b7ce9c

Suspecting https://codereview.chromium.org/2576273002 from changelog

@kainino: Please confirm the issue and help in re-assigning if it is not related to your change.

Thanks, will investigate. I'm guessing this is a Linux/Intel specific but I'll try to reproduce on Linux/NVIDIA.

No GPU process crashes, but important logs:
[14984:14984:0628/190706.344324:ERROR:gles2_cmd_decoder.cc(5310)] : Error: 3 for Command kBlitFramebufferCHROMIUM

I'm not able to reproduce on Linux/NVIDIA with 61.0.3141.7:

Version Information
Data exported	6/29/2017, 1:40:45 PM
Chrome version	Chrome/61.0.3141.7
Operating system	Linux 4.4.0-78-generic
Software rendering list version	13.8
Driver bug list version	10.16
ANGLE commit id	579d8c7dfcfa
2D graphics backend	Skia/61 df669811b16e317b307b335822c4c7c881c1d163-
Command Line	/usr/bin/google-chrome-unstable --user-data-dir=/usr/local/google/home/kainino/.config/google-chrome-unstable --flag-switches-begin --flag-switches-end
Driver Information
Initialization time	102
In-process GPU	false
Passthrough Command Decoder	false
Supports overlays	false
Sandboxed	true
GPU0	VENDOR = 0x10de, DEVICE= 0x13bb
Optimus	false
Optimus	false
AMD switchable	false
Driver vendor	Nvidia
Driver version	381.22
Driver date	
Pixel shader version	4.50
Vertex shader version	4.50
Max. MSAA samples	64
Machine model name	
Machine model version	
GL_VENDOR	NVIDIA Corporation
GL_RENDERER	Quadro K620/PCIe/SSE2
GL_VERSION	4.5.0 NVIDIA 381.22

I was unable to reproduce with the configuration below. I noticed that the machine that the issue was reported on has a very old GPU (Intel HD 2500, over 5 years old) and I'm surprised that WebGL 2 is available on it. The error comes from our GPU command buffer, so it seems like there is a Chrome bug here and not a driver issue.

However, since this doesn't seem to repro on newer hardware+driver (or perhaps some other system difference) and isn't a crash, I'm downgrading to P2 for now.

Version Information
Data exported	6/29/2017, 5:56:28 PM
Chrome version	Chrome/59.0.3071.115
Operating system	Linux 4.8.0-58-generic
Software rendering list version	13.8
Driver bug list version	10.102
ANGLE commit id	a9042d3c1952
2D graphics backend	Skia/59 ef6f9c65527412ec4057ea0551f2e051beb94d32
Command Line Args	--flag-switches-begin --flag-switches-end
Driver Information
Initialization time	23
In-process GPU	false
Passthrough Command Decoder	false
Supports overlays	false
Sandboxed	true
GPU0	VENDOR = 0x8086, DEVICE= 0x1916
Optimus	false
Optimus	false
AMD switchable	false
Driver vendor	Mesa
Driver version	17.2.0
Driver date	
Pixel shader version	4.50
Vertex shader version	4.50
Max. MSAA samples	16
Machine model name	
Machine model version	
GL_VENDOR	Intel Open Source Technology Center
GL_RENDERER	Mesa DRI Intel(R) HD Graphics 520 (Skylake GT2)
GL_VERSION	4.5 (Core Profile) Mesa 17.2.0-devel