summaryrefslogtreecommitdiffstats
path: root/content/browser/gpu/gpu_data_manager_impl.h
Commit message (Collapse)AuthorAgeFilesLines
* Clean up mac gpu switching code a little.zmo@chromium.org2014-04-151-0/+4
| | | | | | | | | | | | | | | | This may not helps with the crash we observed in the bug report, but at least the code is more testable. Also, re-enable the gpu_data_manager_impl_private_unittest.cc which was accidently disabled. BUG=361991 TEST=content_unittests R=kbr@chromium.org Review URL: https://codereview.chromium.org/237903002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@263971 0039d316-1c4b-4281-b951-d872f2087c98
* Move CommandLine to base namespace.brettw@chromium.org2014-03-171-4/+7
| | | | | | | | | | | | Fix all forward-declares and header files referencing CommandLine. This keeps a "using base::CommandLine" in the command line header file so that the rest of the source files can be changes in a follow-up. TBR=sky Review URL: https://codereview.chromium.org/196413016 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@257514 0039d316-1c4b-4281-b951-d872f2087c98
* Move multisampling control from gpu blacklist to driver bug workaround list.zmo@chromium.org2014-02-151-2/+1
| | | | | | | | | BUG=330785 TEST=bots Review URL: https://codereview.chromium.org/135273002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251591 0039d316-1c4b-4281-b951-d872f2087c98
* Remove Windows accelerated surface support.jbauman@chromium.org2014-01-271-6/+0
| | | | | | | | | | Presentation now only happens directly from the GPU process, so this code isn't used anymore. BUG=325947 Review URL: https://codereview.chromium.org/140173004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@247312 0039d316-1c4b-4281-b951-d872f2087c98
* Merge gpu_switching_list into gpu_driver_bug_list.zmo@chromium.org2013-11-051-3/+0
| | | | | | | | | | BUG=314901 TEST=gpu_unittests R=bajones@chromium.org, kbr@chromium.org, piman@chromium.org, sievers@chromium.org Review URL: https://codereview.chromium.org/57633007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@233143 0039d316-1c4b-4281-b951-d872f2087c98
* Disable WebViewTest.Shim(resize-related) tests in software compositing mode.gab@chromium.org2013-09-231-2/+1
| | | | | | | | | BUG=295801 R=fsamuel@chromium.org, jbauman@chromium.org, joi@chromium.org, zmo@chromium.org Review URL: https://codereview.chromium.org/23726050 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@224807 0039d316-1c4b-4281-b951-d872f2087c98
* Added GPU driver workaround for OSX multimonitor multisampling disablingbajones@chromium.org2013-08-301-0/+2
| | | | | | | | BUG=280905 Review URL: https://chromiumcodereview.appspot.com/23473003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@220495 0039d316-1c4b-4281-b951-d872f2087c98
* Update include paths in content/browser for base/process changes.rsesek@chromium.org2013-07-231-1/+1
| | | | | | | | | BUG=242290 TBR=sky@chromium.org Review URL: https://codereview.chromium.org/19495006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@213225 0039d316-1c4b-4281-b951-d872f2087c98
* Enable browser software compositor when GL context can't be used.jbauman@chromium.org2013-07-091-0/+2
| | | | | | | | | | If a GL context can't be created or accelerated compositing is blacklisted, the browser compositor should fall back to software instead of popping up an error. The renderer will use the old 2d path in this case. BUG=253113 Review URL: https://chromiumcodereview.appspot.com/18034022 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@210478 0039d316-1c4b-4281-b951-d872f2087c98
* Use a direct include of time headers in content/, part 1.avi@chromium.org2013-06-281-1/+1
| | | | | | | | | | BUG=254986 TEST=none TBR=ben@chromium.org Review URL: https://codereview.chromium.org/18152002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@209148 0039d316-1c4b-4281-b951-d872f2087c98
* Make sure if GPU process fails to launch, all observers waiting for full gpu ↵zmo@chromium.org2013-06-201-0/+3
| | | | | | | | | | | | | | | | info get a response. Try to reland this CL. Original review is in https://codereview.chromium.org/12335100. The original CL was landed in r184995 and was reverted in 185004 due to some test failures on vista. BUG=174296 TEST=AutofillRiskFingerprintTest.GetFingerprint TBR=apatrick@chromium.org Review URL: https://codereview.chromium.org/17003011 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@207510 0039d316-1c4b-4281-b951-d872f2087c98
* Updated OSX to blacklist multisampling when multiple monitors are connectedbajones@chromium.org2013-06-041-0/+3
| | | | | | | | | BUG=237931 R=joi@chromium.org, kbr@chromium.org, zmo@chromium.org Review URL: https://codereview.chromium.org/14947002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@203827 0039d316-1c4b-4281-b951-d872f2087c98
* Add driver bug workarounds to about:gpu page.zmo@chromium.org2013-05-311-2/+6
| | | | | | | | | | | | | | Also, fixed a few issues in about:gpu 1) get rid of the multi-tab stuff - it's causing a Uncaught TypeError. 2) set the body margin correctly BUG=244576 TEST=about:gpu page with driver bug workarounds info R=gman@chromium.org, nduca@chromium.org Review URL: https://codereview.chromium.org/15650017 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@203274 0039d316-1c4b-4281-b951-d872f2087c98
* Move GPU device/driver info related code from content to gpu.zmo@chromium.org2013-05-231-6/+6
| | | | | | | | | | | | | | | | | | | | Try to reland r201380 with build fix. This has been suggested by gman, and agreed by kbr and jam, for the following reasons: 1) These are gpu related code, and are independent of content / browser, so putting them under gpu/ is the right thing to do conceptually. 2) This enables us to set up tests in various places with the correct blacklisting/driver_bug_workarounds information. Otherwise, for the moment, gpu/ has no visibility into content/ side, so we have to duplicate the driver_bug_workarounds code and hardwire them for testing purpose. This is going to cause a lot of bugs in the future, as we have the two pieces of code for the same thing (one for chrome and one for testing) and people will easily forget to update one or the other. As for this patch, I didn't change the logic, and try to minimize the refactoring. All improvements enabled by this relocation will be done in follow-up CLs. BUG=230477 TEST=tree TBR=apatrick@chromium.org, joi@chromium.org, kbr@chromium.org, piman@chromium.org, sky@chromium.org Review URL: https://codereview.chromium.org/15745014 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@201875 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 201380 "Move GPU device/driver info related code from con..."zmo@chromium.org2013-05-211-6/+6
| | | | | | | | | | | | | | | | | | | | | | | | > Move GPU device/driver info related code from content to gpu. > > This has been suggested by gman, and agreed by kbr and jam, for the following reasons: > > 1) These are gpu related code, and are independent of content / browser, so putting them under gpu/ is the right thing to do conceptually. > > 2) This enables us to set up tests in various places with the correct blacklisting/driver_bug_workarounds information. Otherwise, for the moment, gpu/ has no visibility into content/ side, so we have to duplicate the driver_bug_workarounds code and hardwire them for testing purpose. This is going to cause a lot of bugs in the future, as we have the two pieces of code for the same thing (one for chrome and one for testing) and people will easily forget to update one or the other. > > As for this patch, I didn't change the logic, and try to minimize the refactoring. All improvements enabled by this relocation will be done in follow-up CLs. > > BUG=230477 > TEST=tree > TBR=gman@chromium.org, joi@chromium.org, kbr@chromium.org, piman@chromium.org > > Review URL: https://codereview.chromium.org/15385003 TBR=zmo@chromium.org Review URL: https://codereview.chromium.org/15619004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@201386 0039d316-1c4b-4281-b951-d872f2087c98
* Move GPU device/driver info related code from content to gpu.zmo@chromium.org2013-05-211-6/+6
| | | | | | | | | | | | | | | | | | This has been suggested by gman, and agreed by kbr and jam, for the following reasons: 1) These are gpu related code, and are independent of content / browser, so putting them under gpu/ is the right thing to do conceptually. 2) This enables us to set up tests in various places with the correct blacklisting/driver_bug_workarounds information. Otherwise, for the moment, gpu/ has no visibility into content/ side, so we have to duplicate the driver_bug_workarounds code and hardwire them for testing purpose. This is going to cause a lot of bugs in the future, as we have the two pieces of code for the same thing (one for chrome and one for testing) and people will easily forget to update one or the other. As for this patch, I didn't change the logic, and try to minimize the refactoring. All improvements enabled by this relocation will be done in follow-up CLs. BUG=230477 TEST=tree TBR=gman@chromium.org, joi@chromium.org, kbr@chromium.org, piman@chromium.org Review URL: https://codereview.chromium.org/15385003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@201380 0039d316-1c4b-4281-b951-d872f2087c98
* Refactor GpuDataManagerImpl to make it thread-safe.zmo@chromium.org2013-05-151-128/+37
| | | | | | | | | | | | | | Try to reland after linux build fix. The original review is in https://codereview.chromium.org/14981007/ and https://codereview.chromium.org/14794006/. BUG=232556 TBR=kbr@chromium.org Review URL: https://codereview.chromium.org/14573012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@200131 0039d316-1c4b-4281-b951-d872f2087c98
* Revert "Refactor GpuDataManagerImpl to make it thread-safe."zea@chromium.org2013-05-141-37/+128
| | | | | | | | | | | | Breaks compile on Linux ChromiumOS Builder http://build.chromium.org/p/chromium.chromiumos/builders/Linux%20ChromiumOS%20Builder/builds/42709/steps/compile/logs/stdio#error1 TBR=zmo@google.com BUG=232556 Review URL: https://codereview.chromium.org/15175004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@200087 0039d316-1c4b-4281-b951-d872f2087c98
* Refactor GpuDataManagerImpl to make it thread-safe.zmo@google.com2013-05-141-128/+37
| | | | | | | | | | | | | Try to reland r199530 after fixing an issue that causes Mac Debug to crash when switching GPUs. The original review can be found here: https://codereview.chromium.org/14794006/ BUG=232556 TBR=joi@chromium.org, kbr@chromium.org, piman@chromium.org Review URL: https://codereview.chromium.org/14981007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@200086 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 199530 "Refactor GpuDataManagerImpl to make it thread-saf..."kbr@chromium.org2013-05-131-36/+128
| | | | | | | | | | | | | | | | | | | | | | Caused browser process crashes on dual-GPU Macs. > Refactor GpuDataManagerImpl to make it thread-safe, now and forever. > > The original impl of GpuDataManagerImpl is thread-safe, but gradurally it regressed. > > In order to make sure this class is thread-safe in the future, we move all code to GpuDataManagerImplPrivate, and make GpuDataManagerImpl a simple wrapper around GpuDataManagerImplPrivate's public functions, where each function call is guarded by lock, thus thread-safe. > > BUG=232556 > TEST=asan bots no longer crashes as described in crbug.com/232556 > R=joi@chromium.org, kbr@chromium.org, piman@chromium.org > > Review URL: https://codereview.chromium.org/14794006 TBR=zmo@chromium.org Review URL: https://codereview.chromium.org/15043006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@199770 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 199551 "Reland "Clean up software compositing switches" p..."kalman@chromium.org2013-05-121-1/+0
| | | | | | | | | | | | | | | | | | | | | | | Broke Win Aura: http://build.chromium.org/p/chromium.win/builders/Win%20Aura%20Tests%20%281%29/builds/3836 Try jobs failed too: http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=win7_aura&number=38939 > Reland "Clean up software compositing switches" patch. > > After this patch just --disable-gpu should be enough to put Chrome in software compositing mode for Aura builds. > > TBR=piman@chromium.org,jamesr@chromium.org,jochen@chromium.org > BUG=229712, 230120 > > Review URL: https://codereview.chromium.org/15048003 TBR=skaslev@chromium.org Review URL: https://codereview.chromium.org/14822009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@199632 0039d316-1c4b-4281-b951-d872f2087c98
* Reland "Clean up software compositing switches" patch.skaslev@chromium.org2013-05-101-0/+1
| | | | | | | | | | | After this patch just --disable-gpu should be enough to put Chrome in software compositing mode for Aura builds. TBR=piman@chromium.org,jamesr@chromium.org,jochen@chromium.org BUG=229712, 230120 Review URL: https://codereview.chromium.org/15048003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@199551 0039d316-1c4b-4281-b951-d872f2087c98
* Refactor GpuDataManagerImpl to make it thread-safe, now and forever.zmo@chromium.org2013-05-101-128/+36
| | | | | | | | | | | | | | The original impl of GpuDataManagerImpl is thread-safe, but gradurally it regressed. In order to make sure this class is thread-safe in the future, we move all code to GpuDataManagerImplPrivate, and make GpuDataManagerImpl a simple wrapper around GpuDataManagerImplPrivate's public functions, where each function call is guarded by lock, thus thread-safe. BUG=232556 TEST=asan bots no longer crashes as described in crbug.com/232556 R=joi@chromium.org, kbr@chromium.org, piman@chromium.org Review URL: https://codereview.chromium.org/14794006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@199530 0039d316-1c4b-4281-b951-d872f2087c98
* Provide a reason why GPU access is blocked.zmo@chromium.org2013-05-071-1/+1
| | | | | | | | | | | | | | This provides better information in about:gpu, which helps us to better diagnose GPU feature failures. Also, move the gpu access blocked message to the top as this is the most important message as compared with individual blacklist entry messages. BUG=237393 TEST=about:gpu shows gpu process fails to launch because of settings where gpu is turned off R=joi@chromium.org, kbr@chromium.org, sky@chromium.org, thestig@chromium.org Review URL: https://codereview.chromium.org/14697014 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@198570 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 197751 "Clean up software compositing switches. "kinuko@chromium.org2013-05-021-5/+1
| | | | | | | | | | | | | | | | | | | | > Clean up software compositing switches. > > After this patch just --disable-gpu should be enough to put Chrome in software compositing mode for Aura builds. > > Relanding https://codereview.chromium.org/13985036 which got a speculative revert. > > TBR=piman@chromium.org,jamesr@chromium.org,jochen@chromium.org > NOTRY=true > BUG=229712,230120 > > Review URL: https://chromiumcodereview.appspot.com/14598004 TBR=skaslev@chromium.org Review URL: https://codereview.chromium.org/14620006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@197812 0039d316-1c4b-4281-b951-d872f2087c98
* Clean up software compositing switches. skaslev@chromium.org2013-05-021-1/+5
| | | | | | | | | | | | | | After this patch just --disable-gpu should be enough to put Chrome in software compositing mode for Aura builds. Relanding https://codereview.chromium.org/13985036 which got a speculative revert. TBR=piman@chromium.org,jamesr@chromium.org,jochen@chromium.org NOTRY=true BUG=229712,230120 Review URL: https://chromiumcodereview.appspot.com/14598004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@197751 0039d316-1c4b-4281-b951-d872f2087c98
* Move WebPreferences to root namespace gman@chromium.org2013-05-011-4/+1
| | | | | | | | | | | This is in preparation to using the IPC_STRUCT_XXX macros BUG=235200 TBR=darin@chromium.org,brettw@chromium.org Review URL: https://chromiumcodereview.appspot.com/14364006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@197659 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 197493 "Clean up software compositing switches. "tzik@chromium.org2013-05-011-5/+1
| | | | | | | | | | | | | | | | | | > Clean up software compositing switches. > > After this patch just --disable-gpu should be enough to put Chrome in software compositing mode for Aura builds. > > NOTRY=true > > BUG=229712, 230120 > > Review URL: https://chromiumcodereview.appspot.com/13985036 TBR=skaslev@chromium.org Review URL: https://codereview.chromium.org/14769002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@197599 0039d316-1c4b-4281-b951-d872f2087c98
* Clean up software compositing switches. skaslev@chromium.org2013-04-301-1/+5
| | | | | | | | | | | | After this patch just --disable-gpu should be enough to put Chrome in software compositing mode for Aura builds. NOTRY=true BUG=229712, 230120 Review URL: https://chromiumcodereview.appspot.com/13985036 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@197493 0039d316-1c4b-4281-b951-d872f2087c98
* Renamed 'software_rendering' to 'swiftshader' to differentiate fromskaslev@chromium.org2013-04-231-7/+7
| | | | | | | | | | the new Skia software compositing mode. BUG=230120 Review URL: https://chromiumcodereview.appspot.com/14146011 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@195881 0039d316-1c4b-4281-b951-d872f2087c98
* Don't collect GL string on Mac unless about:gpu is open.zmo@chromium.org2013-04-111-0/+10
| | | | | | | | | | | BUG=222934 TEST=gpu waterfall http://www.webkit.org/blog-files/3d-transforms/poster-circle.html https://www.khronos.org/registry/webgl/sdk/demos/google/san-angeles/ Review URL: https://chromiumcodereview.appspot.com/13818034 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@193524 0039d316-1c4b-4281-b951-d872f2087c98
* Use GpuDriverBugList to manage all the workarounds.zmo@chromium.org2013-04-041-0/+2
| | | | | | | | | | | Before the workarounds are hardwired in feature_info.cc. Now the workarounds are expressed as entries in gpu_driver_bug_list.json. BUG=222857 TEST=gpu_unittests,content_unittests Review URL: https://codereview.chromium.org/13594007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192406 0039d316-1c4b-4281-b951-d872f2087c98
* Change GpuControlList features from bits of int to set.zmo@chromium.org2013-04-021-5/+17
| | | | | | | | | | Before, we limit to manage 32 features. Now we can manage as many as we want. BUG=222857 TEST=content_unittests, waterfall Review URL: https://codereview.chromium.org/13240002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@191858 0039d316-1c4b-4281-b951-d872f2087c98
* Generalzie GpuBlacklist to GpuControlList.zmo@chromium.org2013-03-221-0/+8
| | | | | | | | | | | | | | | This CL refactor the GpuBlacklist so it can be configured to handle a different set of features. So it can handle not only blacklist, but dual gpu switching, and driver bugs. I will add the code to truly manage driver bug workarounds in the next CL. BUG=222857 TEST=content_unittests TBR=asargent Review URL: https://codereview.chromium.org/12976004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@189889 0039d316-1c4b-4281-b951-d872f2087c98
* Add a callback to GpuDataManagerObserver for when a GPU host crashes.jochen@chromium.org2013-03-141-0/+3
| | | | | | | | | | | | | | If this happens during layout tests, we'll just return incorrect pixel results. With this new callback, we can instead correctly report a crash BUG=111316 R=piman@chromium.org TEST=WebKit (content shell) Mac bot has less image failures (but lots more crashes) Review URL: https://codereview.chromium.org/12823003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@188048 0039d316-1c4b-4281-b951-d872f2087c98
* Delete memory manager dead code.ccameron@chromium.org2013-03-121-2/+0
| | | | | | | | | | | | | | | | | There have existed two paths in the memory manager for a few months -- the old path which uniformly distributes all memory across all visible renderers, and the new path which takes into account the needs of each renderer. The transition was made from the old policy to the new policy quite a while ago, so we can safely get rid of the old policy. BUG=150883 Review URL: https://chromiumcodereview.appspot.com/12475002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@187678 0039d316-1c4b-4281-b951-d872f2087c98
* Add a user pref in Settings to disable all GPU features.zmo@chromium.org2013-03-121-5/+3
| | | | | | | | BUG=173130 TEST=about:settings Review URL: https://codereview.chromium.org/12593005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@187666 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 184995abodenha@chromium.org2013-02-271-5/+0
| | | | | | | | | | | | | | | Looks to have caused the broken tests in http://build.chromium.org/p/chromium.win/builders/Vista%20Tests%20%282%29/builds/32494 > Make sure if GPU process fails to launch, all observers waiting for full gpu info get a response. > > BUG=174296 > TEST=AutofillRiskFingerprintTest.GetFingerprint > Review URL: https://codereview.chromium.org/12335100 TBR=zmo@chromium.org Review URL: https://codereview.chromium.org/12310178 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@185004 0039d316-1c4b-4281-b951-d872f2087c98
* Make sure if GPU process fails to launch, all observers waiting for full gpu ↵zmo@chromium.org2013-02-271-0/+5
| | | | | | | | | | info get a response. BUG=174296 TEST=AutofillRiskFingerprintTest.GetFingerprint Review URL: https://codereview.chromium.org/12335100 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@184995 0039d316-1c4b-4281-b951-d872f2087c98
* Fix layering violation in content\browser\renderer_host. That directory ↵jam@chromium.org2013-02-261-1/+10
| | | | | | | | | | | shouldn't be including web_contents. It looks like this regressed because we forgot to update the DEPS exclusion after the tab_contents->web_contents rename. I've fixed the non test case, added exclusion for tests, and put a temporary workaround for the media subdirectory. It seems that the media subdirectory should move to content\browser since it has dependencies on web_contents. Review URL: https://codereview.chromium.org/12319119 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@184735 0039d316-1c4b-4281-b951-d872f2087c98
* Move file_path.h to base/files.brettw@chromium.org2013-02-241-1/+1
| | | | | | TBR=sky git-svn-id: svn://svn.chromium.org/chrome/trunk/src@184344 0039d316-1c4b-4281-b951-d872f2087c98
* Use base namespace for FilePath in content/browserbrettw@chromium.org2013-02-071-2/+2
| | | | | | Review URL: https://codereview.chromium.org/12213066 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@181349 0039d316-1c4b-4281-b951-d872f2087c98
* Hide methods from public GpuDataManager interface that don't need to be ↵jam@chromium.org2013-01-311-7/+21
| | | | | | | | | | | exposed anymore, now that chrome://gpu is in content. I also resorted the methods in gpu_data_manager_impl.cc to match the order in gpu_data_manager.h BUG=169170 Review URL: https://codereview.chromium.org/12122002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@179949 0039d316-1c4b-4281-b951-d872f2087c98
* Relanding r172627zmo@chromium.org2012-12-171-0/+6
| | | | | | | | | | | | | | | | | Can't reproduce the issue that's encountered by shawnsingh anymore. Original CL text: Cache GL strings from GPU process and use them at next browser startup. So we can make complete GPU blacklist decisions at browser startup time. BUG=164728 TEST= TBR=kbr,shawnsingh Review URL: https://codereview.chromium.org/11612008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@173564 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 172627shawnsingh@google.com2012-12-121-6/+0
| | | | | | | | | | | | | | | > Cache GL strings from GPU process and use them at next browser startup. > > So we can make complete GPU blacklist decisions at browser startup time. > > BUG=164728 > TEST= > Review URL: https://codereview.chromium.org/11446080 TBR=zmo@chromium.org Review URL: https://codereview.chromium.org/11549022 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@172644 0039d316-1c4b-4281-b951-d872f2087c98
* Cache GL strings from GPU process and use them at next browser startup.zmo@chromium.org2012-12-121-0/+6
| | | | | | | | | | So we can make complete GPU blacklist decisions at browser startup time. BUG=164728 TEST= Review URL: https://codereview.chromium.org/11446080 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@172627 0039d316-1c4b-4281-b951-d872f2087c98
* CrOS: Add hotkey for disabling the GPU watchdog timer.backer@chromium.org2012-11-301-0/+1
| | | | | | | | | | | | This works around the fact that switching to VT1 on CrOS prevents swaps from clearing, which hangs the GPU process, which causes the GPU process to get killed. Sometimes in order to diagnose a problem, we want to switch to VT1. This hotkey allows a developer to do that. TEST=by hand; Ctrl-Shift-Alt-G; then go about://gpuhang; UI should freeze and not unstick after 10 seconds BUG=chromium-os:28253 Review URL: https://chromiumcodereview.appspot.com/11348099 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@170309 0039d316-1c4b-4281-b951-d872f2087c98
* Add GPU memory to memory monitordavemoore@chromium.org2012-11-211-0/+2
| | | | | | | | | | BUG=None TEST=None TBR=jam@chromium.org Review URL: https://codereview.chromium.org/11419081 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@169126 0039d316-1c4b-4281-b951-d872f2087c98
* Raise an infobar and deny access to WebGL if a GPU reset was detected while ↵kbr@chromium.org2012-11-201-1/+69
| | | | | | | | | | | | | | | | a web page containing WebGL content was visible. The same mechanism will work for Pepper 3D but has not been hooked up for that API yet. https://bugs.webkit.org/show_bug.cgi?id=101826 added the hooks out through the Chromium WebKit API. BUG=125125 TEST=GPUCrashTest.ContextLossRaisesInfobar Review URL: https://chromiumcodereview.appspot.com/11378008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@168794 0039d316-1c4b-4281-b951-d872f2087c98
* Remove calling into CGLQueryRendererInfo to decide dual gpu supporting.zmo@google.com2012-11-141-1/+1
| | | | | | | | | | | | We use the GPU numbers collected through IOKit to make the decision instead. Also, clean the gpu_info_ in GPU process before calling into GPU collection, otherwise we will see integrated GPU gets accumulated incorrectly in each collection. BUG=155938 TEST=bot, mac with dual GPUs Review URL: https://codereview.chromium.org/11358225 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@167767 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-03-23 07:59:44 +0000