Same error: Version 65.0.3325.146 (Official Build) (64-bit) stable 

Works: Version 66.0.3359.22 (Official Build) dev (64-bit) dev 
Works: Version 67.0.3367.0 (Official Build) canary (64-bit) canary

@Reporter: Could you please elaborate on what is expected behavior? Are you seeing this issue on any particular webpage, If so please provide sample URL to test this issue and proper steps to reproduce this issue from TE end.

The WebGL does not work on stable/beta versions. See attachment of the chrome://gpu panel. No website is able to use WebGL at all.

I have installed Dev and Canary builds and webgl works in those builds.

Could it be a profile relates issue that prevents my installation to use WebGL? What is this "too many crashes" means exactly? Is there a counter i should reset here to get WebGL working again? Or is it a boot time failure that means these chrome builds are unable to use webgl at all?

Thanks for your interest in this issue report.

Deleted: 2018-03-12 15_44_22-chrome___gpu.png 42.1 KB

	2018-03-12 15_44_22-chrome___gpu.png 42.1 KB View Download

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

It sounds like two issues

1) User is getting SwiftShader with a newer GPU.
2) SwiftShader is crashing.

Reporter: could you please navigate to 'about:crashes' and tell us the most recent crash ids?

Could you try running chrome with a clean user profile, by specifying a temporary directory such as: chrome.exe --user-data-dir=c:\temp\chrome

FWIW, I tried running Chrome 65.0.3325.146 with --disable-gpu on Windows 7, and http://webglsamples.org/aquarium/aquarium.html rendered fine. So SwiftShader itself is probably OK, but something else is causing GPU process crashes.

Local Crash ID 9acc72ef-b3b0-49f4-97c9-578a9db6a0a8
Crash report captured on Tuesday, January 16, 2018 at 3:05:04 AM was not uploaded

Local Crash ID f8525731-e592-4bfa-ae77-7243c6df5f31
Crash report captured on Thursday, January 11, 2018 at 9:17:47 PM was not uploaded

Local Crash ID 2d302e1f-02bf-4c55-98fb-a7ecd29679b0
Crash report captured on Saturday, December 23, 2017 at 1:59:06 AM was not uploaded

-

The captures appear to be fairly old. I don't think they would be relevant, since 4 weeks ago most definitely was working. But i'd say pre-update it was working for me.

"clean user profile" allows me to use webgl, so this could be a profile related issue as it would seem. Can i fix this locally without loosing all profile data i currently have?

-

--disable-gpu does not provide me access the content on the url, it says webgl is unavailable. i can confirm the cmd flag is accepted by visiting the chrome://version where it shows up.

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Can you provide the about:gpu content? and then run chrome with --disable-software-rasterizer, and provide the about:gpu content?

Re #8: It looks like these crash reports are not uploaded to our servers.  It would be useful if you could enable crash reporting following the steps at https://support.google.com/chrome/answer/96817, and letting us know the crash IDs if you experience more issues.

The crash reports page should show something like "Uploaded Crash Report ID 0123456789abc".

zmo@, as the most recent crash reports above are from January 16, is it possible that we may be getting stuck without GPU support based on cached data?

I just checked. Cached data logic was removed before M65 branch point.

We will need about:gpu page content to understand why we fall back to SwiftShader in the first place.

Adding Needs-Feedback label as per comments #10...#13 and requesting reporter to provide Chrome://gpu details and try as per comment#10.

Thanks!

zmo@ , i actually was running chrome with the --disable-software-rasterizer the whole time. It was a chrome://flags setting. I removed this setting and it no longer shows up in the chrome://version either.

The WebGL is functioning again.

Do you still want me to copy the full gpu output? Everything seems to be working. Except maybe a few lines at the end.

Please let me know if you require further informations in this case.

Deleted: 2018-03-14 17_37_15-chrome___gpu.png 51.1 KB

	2018-03-14 17_37_15-chrome___gpu.png 51.1 KB View Download

Deleted: 2018-03-14 17_37_08-chrome___gpu.png 43.3 KB

	2018-03-14 17_37_08-chrome___gpu.png 43.3 KB View Download

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

taligahack@gmail.com: yes, we still need about:gpu content with and without --disable-software-rasterizer.

Now likely you are still running with SwiftShader, so it's less performant than hardware GPU. We want to understand why you fall back to SwiftShader in the first place.

I have attached the about:gpu outputs as per requested. 

The interesting thing for me, i was running chrome for years with the setting of disabled software rasterizer. Strange that it cause troubles with the HW rendering since update.

Please let me know if i can provide you with further informations.

Deleted: about_gpu_normal.txt 16.0 KB

about_gpu_normal.txt 16.0 KB View Download

Deleted: about_gpu_disable_software_raster.txt 4.3 KB

about_gpu_disable_software_raster.txt 4.3 KB View Download

It looks like a bug I already fixed in https://chromium-review.googlesource.com/c/chromium/src/+/920501

Very few people use --disable-software-rasterizer, that's why I didn't merge the fix back to M65.

You can just run Chrome without this flag. Everything should be fine.

Also, I highly recommend not pass in --ignore-gpu-blacklist.