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

Issue 774000 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Dec 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug

Blocked on:
issue 744658



Sign in to add a comment

Chrome is not using the GPU even though I have a relatively modern GPU and latest drivers

Reported by hidenny...@gmail.com, Oct 12 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36

Steps to reproduce the problem:
1. Get a computer with both intel hd graphics 630 and nvidia gtx 950m

What is the expected behavior?
chrome uses the gpu for most things

What went wrong?
chrome doesn't use the gpu for anything

Did this work before? N/A 

Chrome version: 61.0.3163.100  Channel: stable
OS Version: 10.0
Flash Version: 

attached about:gpu output. system is in japanese mode, windows 10 home, v1703
 
gpu.html
49.2 KB View Download

Comment 1 by gman@chromium.org, Oct 12 2017

Cc: zmo@chromium.org
This might be something obvious but a I don't see why chrome is not letting this person use the GPU. It's running the latest nvidia drivers, it's got a decent gpu. I don't see a message about it being blacklisted. Instead I see something about the GPU must be Intel, AMD, or NVidia which it is.

Wondering if the issue has something to do with the machine being japanese?

Comment 2 by zmo@chromium.org, Oct 12 2017

Blockedon: 744658
Cc: -zmo@chromium.org
Components: Internals>GPU>Internals
Owner: zmo@chromium.org
Status: Assigned (was: Unconfirmed)
No, it's due to browser and GPU process blacklisting discrepancy that triggered the swiftshader.

Once  crbug.com/744658  is done, this will automatically be fixed.

I am getting there soon.

Comment 3 by zmo@chromium.org, Oct 12 2017

Cc: kbr@chromium.org vmi...@chromium.org piman@chromium.org
Another bug though, this seems like an OPTIMUS, only Chrome isn't detecting it.
Project Member

Comment 4 by bugdroid1@chromium.org, Dec 15 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/16d39b876bdf2560e499afe4625d02da76d3cd44

commit 16d39b876bdf2560e499afe4625d02da76d3cd44
Author: Zhenyao Mo <zmo@chromium.org>
Date: Fri Dec 15 22:48:04 2017

Get rid of GL string cache on non-Android platform

and no longer blacklist GPU access if preliminary GPU feature decisions differ
from full info decisions.

The reason we can do this now, is because the only GPU feature check that's not
from GPU process is kDisableAcceleratedVideoDecode on Android. There is no
decision difference on Android between preliminary and full info.

This should get quite a few Windows machines putting to SwiftShader back to
GPU acceleration.

BUG= 744658 , 764290 ,766190, 774000 , 793845 
TEST=bots
R=piman@chromium.org,kbr@chromium.org

Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
Change-Id: I3fae7ff326a9cf2ea5b23c56261cb3139416a38f
Reviewed-on: https://chromium-review.googlesource.com/828040
Commit-Queue: Zhenyao Mo <zmo@chromium.org>
Reviewed-by: Lei Zhang <thestig@chromium.org>
Reviewed-by: Antoine Labour <piman@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524497}
[modify] https://crrev.com/16d39b876bdf2560e499afe4625d02da76d3cd44/chrome/browser/BUILD.gn
[modify] https://crrev.com/16d39b876bdf2560e499afe4625d02da76d3cd44/chrome/browser/browser_process.h
[modify] https://crrev.com/16d39b876bdf2560e499afe4625d02da76d3cd44/chrome/browser/browser_process_impl.cc
[modify] https://crrev.com/16d39b876bdf2560e499afe4625d02da76d3cd44/chrome/browser/browser_process_impl.h
[modify] https://crrev.com/16d39b876bdf2560e499afe4625d02da76d3cd44/chrome/browser/chrome_browser_main.cc
[delete] https://crrev.com/c0e53b734bb3b198e7fece89b477467d84102aa2/chrome/browser/gpu/gl_string_manager.cc
[delete] https://crrev.com/c0e53b734bb3b198e7fece89b477467d84102aa2/chrome/browser/gpu/gl_string_manager.h
[modify] https://crrev.com/16d39b876bdf2560e499afe4625d02da76d3cd44/chrome/browser/gpu/gpu_driver_info_manager_android.cc
[modify] https://crrev.com/16d39b876bdf2560e499afe4625d02da76d3cd44/chrome/browser/gpu/gpu_driver_info_manager_android.h
[delete] https://crrev.com/c0e53b734bb3b198e7fece89b477467d84102aa2/chrome/browser/gpu/gpu_profile_cache.h
[modify] https://crrev.com/16d39b876bdf2560e499afe4625d02da76d3cd44/chrome/browser/prefs/browser_prefs.cc
[modify] https://crrev.com/16d39b876bdf2560e499afe4625d02da76d3cd44/chrome/test/base/testing_browser_process.cc
[modify] https://crrev.com/16d39b876bdf2560e499afe4625d02da76d3cd44/chrome/test/base/testing_browser_process.h
[modify] https://crrev.com/16d39b876bdf2560e499afe4625d02da76d3cd44/content/browser/gpu/gpu_data_manager_impl.cc
[modify] https://crrev.com/16d39b876bdf2560e499afe4625d02da76d3cd44/content/browser/gpu/gpu_data_manager_impl.h
[modify] https://crrev.com/16d39b876bdf2560e499afe4625d02da76d3cd44/content/browser/gpu/gpu_data_manager_impl_private.cc
[modify] https://crrev.com/16d39b876bdf2560e499afe4625d02da76d3cd44/content/browser/gpu/gpu_data_manager_impl_private.h
[modify] https://crrev.com/16d39b876bdf2560e499afe4625d02da76d3cd44/content/browser/gpu/gpu_data_manager_impl_private_unittest.cc
[modify] https://crrev.com/16d39b876bdf2560e499afe4625d02da76d3cd44/content/public/browser/gpu_data_manager.h
[modify] https://crrev.com/16d39b876bdf2560e499afe4625d02da76d3cd44/content/renderer/render_thread_impl.cc
[modify] https://crrev.com/16d39b876bdf2560e499afe4625d02da76d3cd44/content/test/gpu/gpu_tests/gpu_process_expectations.py

Comment 5 by zmo@chromium.org, Dec 15 2017

Status: Fixed (was: Assigned)

Sign in to add a comment