New issue
Advanced search Search tips

Issue 621316 link

Starred by 2 users

Issue metadata

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



Sign in to add a comment

--override-use-gl-with-osmesa-for-tests switch not working on windows systems without gpu.

Reported by k...@yandex-team.ru, Jun 18 2016

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 YaBrowser/16.6.0.8326 (beta) Safari/537.36

Steps to reproduce the problem:
Run browser_tests or chromium with --override-use-gl-with-osmesa-for-tests on windows system with no gpu.

What is the expected behavior?
Black screen in tests and "osmesa" driver in chrome://gpu in chromium.

What went wrong?
Browser is running in software compositing mode.

Did this work before? N/A 

Chrome version: 50.0.2661.102  Channel: dev
OS Version: 
Flash Version: Shockwave Flash 22.0 r0
 

Comment 1 by danakj@chromium.org, Jun 19 2016

Cc: danakj@chromium.org vmi...@chromium.org piman@chromium.org
kirr@yandex-team.ru is inestigating
Labels: Te-NeedsFurtherTriage
Components: Internals>GPU
Project Member

Comment 4 by bugdroid1@chromium.org, Jun 28 2016

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

commit 98e5974f32d724c56b27eea7c3ea97599f6ab7e7
Author: kirr <kirr@yandex-team.ru>
Date: Tue Jun 28 06:06:54 2016

Fixed running gpu process with kOverrideUseGLWithOSMesaForTests.

On windows with no graphics card gpu process was not started because
GpuDataManager was considered that there is no gpu and all gpu features
are blacklisted. Make kOverrideUseGLWithOSMesaForTests equal to kUseGL
when check gpu info.

BUG= 621316 

Review-Url: https://codereview.chromium.org/2087283003
Cr-Commit-Position: refs/heads/master@{#402412}

[modify] https://crrev.com/98e5974f32d724c56b27eea7c3ea97599f6ab7e7/components/autofill/content/browser/risk/fingerprint_browsertest.cc
[modify] https://crrev.com/98e5974f32d724c56b27eea7c3ea97599f6ab7e7/content/browser/gpu/gpu_data_manager_impl_private.cc

Is there anything left to fix before we can close this issue?

Comment 6 by danakj@chromium.org, Jun 28 2016

Status: Fixed (was: Unconfirmed)
I think that was it. Thanks very much!

Sign in to add a comment