New issue
Advanced search Search tips

Issue 712509 link

Starred by 1 user
Status: Verified
Owner:
sugoi@chromium.org
Closed: Sep 12
Cc:
capn@chromium.org
zmo@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug

Blocking:
issue 160392



Sign in to add a comment

WebGL does not fall back to SwiftShader in a Chromoting session

Project Member Reported by capn@chromium.org, Apr 18 2017 
When Chromoting to a Linux workstation, I get Gallium 0.4 on llvmpipe renderer from VMware, Inc. as the graphics driver, regardless of whether I launch Chrome with --disable-gpu. WebGL pages don't render properly. Instead we should be falling back to SwiftShader.

Comment 1 by sugoi@chromium.org, Sep 6

Cc: zmo@chromium.org
Is this still an issue?
If so, can we blacklist "Gallium 0.4 on llvmpipe renderer from VMware, Inc." in order to fallback to SwiftShader now that it works in headless?

Comment 2 by zmo@chromium.org, Sep 11 

--disable-gpu should work fine now since I redid this part of Chrome since the bug was created. But capn@, could you please confirm.

Comment 3 by capn@chromium.org, Sep 12

Status: Verified (was: Assigned)
Yes, works great now.
►

Sign in to add a comment