New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 717840 link

Starred by 1 user
Status: Duplicate
Merged: issue 719213
Owner: ----
Closed: May 2017
Cc:
sugoi@chromium.org
vmi...@chromium.org
capn@chromium.org
zmo@chromium.org
█ jbau...@chromium.org
dsinclair@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Hardware Acceleration now longer enabled on AMPGPU

Reported by leebick...@gmail.com, May 3 2017 
UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.96 Safari/537.36

Steps to reproduce the problem:
OS: Arch Linux (x86_64)
Kernel: 4.10.13
Graphics Card: AMD RX 480 (8GB)
Graphics Driver: AMDGPU (not PRO)
Monitor Res: 4K

What is the expected behavior?

What went wrong?
In stable channel (v58) hardware acceleration works fine. However in beta channel (v59) and dev channel (v60) hardware acceleration is not enabled.

I attached the chrome://gpu output of v58 and v59 to show the difference.

Did this work before? Yes 58.0.3029.96

Chrome version: 59.0.3071.29  Channel: beta
OS Version: 
Flash Version:
58.0.3029.96.pdf
103 KB Download
59.0.3071.29.pdf
100 KB Download

Comment 1 by ligim...@chromium.org, May 3 2017

Components: Internals>GPU
Labels: Needs-Triage-M59

Comment 2 by pucchakayala@chromium.org, May 5 2017

Cc: kbr@chromium.org
Labels: Needs-Feedback
Looping in GPU Owners.

Ken, can you pls update us if this is an intended change ?

Comment 3 by kbr@chromium.org, May 5 2017

Cc: -kbr@chromium.org sugoi@chromium.org zmo@chromium.org capn@chromium.org vmi...@chromium.org jbau...@chromium.org
Components: -Internals>GPU Internals>GPU>SwiftShader Internals>GPU>Internals
It looks like the SwiftShader fallback is kicking in, but we aren't getting the real GPU and driver info.

Comment 4 by capn@chromium.org, May 12 2017

Components: -Internals>GPU>SwiftShader
SwiftShader only kicks in when the GPU is blacklisted for WebGL, so there must have been a change in the blacklisting that affects this particular GPU or driver. I don't think a GPU this new is supposed to be blacklisted, unless there's some highly concerning driver bug, so this warrants a deeper look.

zmo@, do you know of any blacklisting changes that could affect this system?

Comment 5 by zmo@chromium.org, May 12 2017

Mergedinto: 719213
Status: Duplicate (was: Unconfirmed)
►

Sign in to add a comment