Chromium doesn't do a good job providing additional details in the webglcontextlost event. This should hopefully be a rare event and will typically only happen if Chromium's GPU process crashes, or if a GPU hang occurs and the system recovers. In these cases you can ask the user to gather the contents of Chromium's about:gpu page and see if anything in the logs points to a root cause. If the context losses are repeatable then please file a bug on
crbug.com under the "Chromium > Blink > WebGL" component with a test case and the output of about:gpu from an affected machine.