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

Issue 760771 link

Starred by 2 users
Status: WontFix
Owner: ----
Closed: Sep 2017
Cc:
█ abdulsyed@chromium.org
█ kbr@chromium.org
gov...@chromium.org
vmi...@chromium.org
pbomm...@chromium.org
chrome-conops-escalation@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 3
Type: Bug



Sign in to add a comment

[Stable Feedback] Chrome forcing discrete GPU even when HW acceleration is turned off

Project Member Reported by hongchic...@chromium.org, Aug 30 2017 
Chrome Version: 60.0.3112.113
OS: Mac OS X: 10.12.6

What steps will reproduce the problem?
User reported after updating to M60 from M59, Chrome automatically use dedicated gpu when starting Chrome even if hardware acceleration is turned OFF. Same thing happened when this user tried Canary.

https://listnr.corp.google.com/report/71613330324


What is the expected result?

What happens instead?

Please use labels and text to provide additional information.


For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.

Comment 1 by manoranj...@chromium.org, Aug 30 2017

Cc: kbr@chromium.org gov...@chromium.org abdulsyed@chromium.org vmi...@chromium.org

Comment 2 by gov...@chromium.org, Aug 30 2017

Cc: pbomm...@chromium.org

Comment 3 by ericrk@chromium.org, Sep 5 2017

Status: WontFix (was: Untriaged)
This may be behaving as expected - if we blacklist the integrated GPU we will always trigger the discrete GPU. It's hard to know for sure if this is the case without additional information (ideally, the contents of about:gpu).

If this turns out to be an integrated GPU which has been blacklisted, we could discuss whether falling back to discrete is appropriate.

At the current time, I don't think this is actionable. Please re-open if we can get the contents of about:gpu from an affected user.
►

Sign in to add a comment