Able to reproduce the issue on Windows 10 using chrome reported version #64.0.3282.167 and latest canary #66.0.3350.0. Issue is not seen in OS-Mac and OS-Linux.

Bisect Information:
=====================
Good build: 64.0.3271.0
Bad Build : 64.0.3272.0

Change Log URL: 
https://chromium.googlesource.com/chromium/src/+log/740a58fe5be72d088743717ebd58883a4e6eb5ee..c041c36e23af74a3f94e74ab20652bc41bf70e6f

angle-deps-roller CL:
https://chromium.googlesource.com/angle/angle.git/+log/2c7f34c833b4..3d70ca9cc194

From the above change log suspecting below change
Change-Id: Ic918bfe8f16460bcd6101d73a7a674145f5aeecd
Reviewed-on: https://chromium-review.googlesource.com/766434

oetuaho@ - Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.
Note: Adding stable blocker for M-64 as it seems to be a recent regression. Please feel free to remove the same if not appropriate.

Thanks...!!

There are many WebGL errors in the execution of this page:
250 WebGL: INVALID_VALUE: uniform1iv: no array
3   Main:1 [.Offscreen-For-WebGL-0x2e0e36d62600]RENDER WARNING: there is no texture bound to the unit 3
    Main:1 [.Offscreen-For-WebGL-0x2e0e36d62600]RENDER WARNING: there is no texture bound to the unit 0
    Main:1 [.Offscreen-For-WebGL-0x2e0e36d62600]RENDER WARNING: there is no texture bound to the unit 3
    Main:1 [.Offscreen-For-WebGL-0x2e0e36d62600]RENDER WARNING: there is no texture bound to the unit 0

In particular, the uniform1iv calls. I suspect that this is a buggy version of Three.js which makes invalid uniform1iv calls when unused uniforms are automatically optimized out of the shader. (That, or you have a bug in your code that's causing that to happen.)

BTW, this is failing for me on Firefox 52 on Linux as well, so this might have been happening all along on all browsers on every platform non-Windows platform (Mac, Linux, Android, and probably even iOS Safari). Have you tested it on other platforms?

Your Three.js version is "65b" but the current revision is "90". Please look into upgrading your Three.js version (at least partially, if not all the way to version 90).
If you find that there is still an issue, comment here.

More testing results:
macOS/Intel/Chrome 64: also completely broken, but in a different way
macOS/Intel/Firefox 59: seems to work

So it's not broken on every configuration.
But all of these configurations do flag the same WebGL errors, so those are the first thing to fix.

Okay, let me track down these errors and see if the problem still persists.  Thank you for getting back so soon.  

Problem persists after I fixed the uniform1iv errors.
Still a few "no texture bound to unit x" errors that I am tracking down.

However, the garbled scene seems to indicate that the shader material for particles created using ANGLE_instanced_arrays has problem generate correct mapping from a global/non-instanced texture (tDiffuse) as below. 

uniform sampler2D tDiffuse;
uniform vec2 size;

void main() {
   
    vec3 txtCoords = vec3(gl_FragCoord.x / size.x, gl_FragCoord.y / size.y, gl_FragCoord.z);

    gl_FragColor = texture2D( tDiffuse, txtCoords );
}


Perhaps it has something to do with removed globals?

Okay, further investigation reveals one of my instanced UV attributes got "optimized out".  So, it indeed leans toward some fault in my code.