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

Issue 852399 link

Starred by 1 user

Issue metadata

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

Blocking:
issue 693090



Sign in to add a comment

--use-angle=gl results in black screen on NVIDIA/Windows

Reported by oetu...@nvidia.com, Jun 13 2018

Issue description

Chrome Version: 69.0.3457.0
OS: Win10

What steps will reproduce the problem?
(1) Start chrome with --use-angle=gl command line parameter. Passthrough command buffer does not seem to matter.

What is the expected result?
Browser renders as usual.

What happens instead?
Browser window is mostly covered with black. Interaction with the browser like resizing the window still seems to work.

This seems to have regressed after Chrome version 67.0.3396.87.

Reproducible with at least GeForce GTX 1080, driver version 398.11. Also reproduced with GTX 970 with slightly earlier drivers.

Does not seem to affect systems with Intel GPU.
 
Blocking: 693090
Cc: oetu...@nvidia.com jmad...@chromium.org
Components: Internals>GPU>ANGLE
Labels: -Pri-2 Pri-1
Owner: geoffl...@chromium.org
Status: Assigned (was: Untriaged)
Labels: Needs-Bisect
Labels: Needs-Triage-M69 Triaged-ET TE-NeedsTriageFromHYD
Unable to reproduce the issue on Win-10 using chrome reported version #69.0.3457.0.

Attached a screen cast for reference.

Following are the steps followed to reproduce the issue.
------------
1. Started chrome with --use-angle=gl command line parameter.
2. Observed that browser rendered as usual.

The issue seems to be reproducible on GeForce GTX 1080, driver version 398.11 and GTX 970. Hence, forwarding the issue to inhouse for further triaging.

Thanks...!!
852399.mp4
8.4 MB View Download
Project Member

Comment 4 by bugdroid1@chromium.org, Jun 14 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/angle/angle/+/9491e5ebed989656c00e5b9434a17e321899b98b

commit 9491e5ebed989656c00e5b9434a17e321899b98b
Author: Geoff Lang <geofflang@chromium.org>
Date: Thu Jun 14 17:44:13 2018

Generate framebuffer IDs used in DXGISwapChainWindowSurfaceWGL.

The DXGI surface was attempting to bind renderbuffers to the default
framebuffer instead of a generated one.

BUG= 852399 

Change-Id: Ibca6699e73e84735c64f2e3ee6b7684bfcbe1bfc
Reviewed-on: https://chromium-review.googlesource.com/1101240
Commit-Queue: Geoff Lang <geofflang@chromium.org>
Commit-Queue: Corentin Wallez <cwallez@chromium.org>
Reviewed-by: Corentin Wallez <cwallez@chromium.org>

[modify] https://crrev.com/9491e5ebed989656c00e5b9434a17e321899b98b/src/libANGLE/renderer/gl/wgl/DXGISwapChainWindowSurfaceWGL.cpp

Status: Fixed (was: Assigned)
Project Member

Comment 6 by bugdroid1@chromium.org, Jun 14 2018

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

commit 7a8d2a318d51a88e18d74216904996ec88a6df0f
Author: angle-chromium-autoroll <angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Date: Thu Jun 14 23:46:40 2018

Roll src/third_party/angle 75359664993b..9491e5ebed98 (1 commits)

https://chromium.googlesource.com/angle/angle.git/+log/75359664993b..9491e5ebed98


git log 75359664993b..9491e5ebed98 --date=short --no-merges --format='%ad %ae %s'
2018-06-14 geofflang@chromium.org Generate framebuffer IDs used in DXGISwapChainWindowSurfaceWGL.


Created with:
  gclient setdep -r src/third_party/angle@9491e5ebed98

The AutoRoll server is located here: https://angle-chromium-roll.skia.org

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.

CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel

BUG= chromium:852399 
TBR=cwallez@chromium.org

Change-Id: I6616599386646d5d6fc021fdb20052993c4aef84
Reviewed-on: https://chromium-review.googlesource.com/1101717
Reviewed-by: angle-chromium-autoroll <angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: angle-chromium-autoroll <angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#567483}
[modify] https://crrev.com/7a8d2a318d51a88e18d74216904996ec88a6df0f/DEPS

Comment 7 by oetu...@nvidia.com, Jun 15 2018

Thanks a lot for the fix!

Can we add basic pixel test coverage for the GL backend, so this won't regress in the same way again?

Sign in to add a comment