Issue metadata
Sign in to add a comment
|
WebGL became unavailable
Reported by
tom.a.br...@gmail.com,
Sep 5 2016
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.89 Safari/537.36 Example URL: https://get.webgl.org/ Steps to reproduce the problem: 1. Go to any WebGL site (eg. https://get.webgl.org/), I want to use tinkercad. 2. WebGL reported to be not working in browser 3. What is the expected behavior? WebGL sites work. What went wrong? Since yesterday I have not been able to use WebGL in Chrome. I had been using tinkercad.com the previous day. I'm not sure if anything upgraded over night. I can still use WebGL in Safari. Does it occur on multiple sites: Yes Is it a problem with a plugin? N/A Did this work before? Yes 2 days ago and previously Does this work in other browsers? Yes Chrome version: 53.0.2785.89 Channel: stable OS Version: OS X 10.10.5 Flash Version: Shockwave Flash 22.0 r0 I have attached output of GPU from Chrome. There is no "Disable WebGL" option in chrome://flags Hardware is accelerated in settings.
,
Sep 6 2016
This is intentional. Too many crashes from Intel HD 3000 so we disabled all GPU stuff on it. You can go to about:flags and enable "Override software rendering list" to get back gpu. However, note that it might reduce the stability for Chrome on your Mac.
,
Sep 7 2016
Would enabling SwiftShader on these systems be of any value?
,
Sep 7 2016
I don't see why not if we use SwiftShader on windows as fallback. The only question is how much work there is to add this.
,
Sep 7 2016
,
Apr 1 2017
Any idea why the flag's no more working? Have Override software rendering list enabled but WebGL doesn't work again since a few days.
,
Apr 5 2017
Please post the content of the chrome://gpu page on the affected system.
,
Apr 28 2018
Here's the chrome://gpu report on my Intel HD 3000: https://pastebin.com/v0qg9rwj The output says the blacklist is related to 2 bugs. I don't have permission to see the first one, but 661596 doesn't apply to my system because my 13" system doesn't have a discrete card (just the integrated one). 661596: https://bugs.chromium.org/p/chromium/issues/detail?id=661596
,
Apr 28 2018
GPU acceleration is disabled on Intel HD 3000, either it's s single GPU system or a dual GPU system.
,
Sep 6
This isn't a SwiftShader issue. Delegating to zmo@, in case this issue still points to an issue other than just enabling SwiftShader on MacOS. If this issue is now only about having SwiftShader on MacOS, then this issue is a duplicate of crbug.com/719257 .
,
Sep 6
Definitely looks like a duplicate to me. Merging. Also blocking on the issue where we blacklisted HD 3000. Since that issue is private, here is a link to the commit that implemented it: https://chromium.googlesource.com/chromium/src.git/+/0b113ce33d9d553b105fa68a2b2b554a93de43e9 |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by tkent@chromium.org
, Sep 5 2016