UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36 Edge/16.16299

Steps to reproduce the problem:
It's a workload test that basically repeats the following steps over and over for about two hours, each runthrough takes about 1-2 minutes:
1. create a new canvas (HTMLCanvasElement)
2. use canvas to display dozens of textures (some textures are stored in GPU memory, some get uploaded every time they are displayed)
3. after about 60-90 seconds we stop using canvas and free all textures
4. test then performs about 30 seconds of non canvas operations before looping back to #1.

Everything happens on the same HTML page, there is no reload or page change involved.
After every runthrough any resource associated with canvas object is freed, but the angular application still holds a reference to that canvas, though it's never reused.
Usually keeping canvas instances results in chrome complaining about too many canvases and informing about releasing / destroying the oldest one (it is unclear whether it's related to problem). 

Our tests use a selenium grid with 8 nodes capable of 8 chrome sessions each. 
One workload test run spawns 30 parallel sessions all performing the steps outlined above, repeatedly, so each selenium node has to handle about 4 sessions.
Issue occurs on a small portion of these 30 sessions (approx. 1-2 per 2h run) and they don't prefer one particular selenium node, and if there is two or more failing, then there is at least two nodes having that issue. Other sessions on the same nodes complete their test runs just fine.

What is the expected behavior?
WebGL initialization ok.

What went wrong?
WebGL cannot be initialized (no hw acceleration available)

Did this work before? No 

Chrome version: 71.0.3578.98  Channel: stable
OS Version: Server 2012 R2 64bit VMWare 6.5
Flash Version:
 

Deleted: GPUDebugOut.txt 15.9 KB

GPUDebugOut.txt 15.9 KB View Download