Please provide the complete contents of about:gpu in plaintext form -- as the bug template requested. Thanks.

CC'ing SwiftShader folks since this could be a good use case.

Unable to reproduce the issue on Mac 10.12.5, Windows 7 & Ubuntu 14.04 using chrome reported version-61.0.3129.0 as per the steps mentioned in comment#0.

Observed "Your browser supports WebGL" text & Seen spinning wireframe cube on the website https://get.webgl.org/ which is working as intended.

Asherkin@,Please find the attached screencast & GPU info for reference & let us know your observations on the same.
Thanks..!!

Deleted: 732754.mp4 1.5 MB

	732754.mp4 1.5 MB View Download

Deleted: Mac GPU.rtf 61.9 KB

Mac GPU.rtf 61.9 KB Download

> Please provide the complete contents of about:gpu in plaintext form -- as the bug template requested. Thanks.

See attachment. The bug template did not request this, perhaps that does not work via the wizard? If you need a plainer-text form, please provide instructions.

> Unable to reproduce the issue on Mac 10.12.5, Windows 7 & Ubuntu 14.04 using chrome reported version-61.0.3129.0 as per the steps mentioned in comment#0.

Your GPU info suggests that you tested on bare metal hardware with a GPU, and thus were not using Apple Software Renderer. I do not know if there is a safe and sane way to disable the GPU on hardware, the easiest way to reproduce would be with a Virtual Machine.

I found these instructions on forcing software rendering on macOS, but they do not appear to work with Chrome (presumably whatever OpenGL Profiler does to force the pixel format does not carry through to the GPU process -- although --single-process didn't work either, maybe someone more familiar with Chrome internals will have more luck).
https://lists.apple.com/archives/quartzcomposer-dev/2010/Jun/msg00090.html

Deleted: Asher Baker - gpu.rtf 56.8 KB

Asher Baker - gpu.rtf 56.8 KB Download

Thank you for providing more feedback. Adding requester "kbr@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

FWIW when running Canary with --gpu-testing-device-id=0x0405 --gpu-testing-vendor-id=0x15ad --gpu-testing-gl-vendor=APPLE --gpu-testing-gl-renderer=Apple on a 2013 MacBook Pro (non-virtualized), about:gpu tells me:

WebGL: Hardware accelerated
WebGL2: Hardware accelerated
VENDOR = 0x15ad, DEVICE= 0x0405 *ACTIVE*
Apple Software Renderer used under VMWare experiences synchronization issues with GPU Raster: 607829
Disabled Features: gpu_rasterization

get.webgl.org shows the spinning cube, and WebGL Aquarium runs at 60 FPS (for reference SwiftShader runs it at 15 FPS in a Windows VM on the same Macbook). So it's using the GPU.

Thanks for the reply.
As per comment#4, we(chrome hyd team) do not have the mentioned configuration from our end, could any one from MTV team please look into this issue.

Adding 'TE-NeedsTriageFromMTV' label for further investigation.

Submitter, apologies, I thought the bug template for new graphics bugs requested the contents of about:gpu.

I attempted to reproduce this on physical hardware with:

/Applications/Google\ Chrome\ Canary.app/Contents/MacOS/Google\ Chrome\ Canary --user-data-dir=/tmp/t1 --use-gl=apple --gpu-testing-device-id=0x0405 --gpu-testing-vendor-id=0x15ad --gpu-testing-gl-vendor=APPLE --gpu-testing-gl-renderer=Apple

Chrome doesn't render correctly in this configuration -- invalidations seem to be missing.

Apologies, but making this work is not a high priority. Getting SwiftShader to work on macOS is a much higher priority and would solve this problem as a side-effect.

Submitter: perhaps Headless Chrome might be a good fit for your use case?

Unfortunately headless chrome doesn't work for me - I have an application built on Electron that renders content with WebGL (if available). The VM in question is my macOS build/test agent (and occasional platform-specific development).

Does it make sense to blacklist Apple Software Renderer for WebGL so that pages can fall back to non-WebGL content? I'll probably look into doing this in my application code for now anyway (so I don't have to wait for any change to propagate down to stable and then an Electron release) as that is probably better than continuing to use Chrome 52.

Updating labels and removing from bisect bucket since TE cannot repro.

kbr@, do you think that just blacklisting WebGL on Apple Software renderer might make sense? Do you know of situations where people are successfully using WebGL on this GPU, or might it just be broken?

ericrk@: I don't seem to be able to reproduce the problem. We can blindly add a blacklist entry for vendor ID 0x15ad and device ID 0x0405 on macOS, but wouldn't be able to test it. I'll prepare a CL.

vmiura@ has a CL in progress disabling all GPU features when the Apple Software Renderer is in use:
https://chromium-review.googlesource.com/636089

There seem to be some test failures with that CL. Let me know if I can help debug them. In the meantime, to clarify that I'm not proceeding with a specific WebGL blacklist, duplicating this bug into the other one.