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

Issue 837013 link

Starred by 1 user
Status: WontFix
Owner:
zmo@chromium.org
Closed: May 2018
Cc:
█ kirish@google.com
sunn...@chromium.org
mdbustos@google.com
ericrk@chromium.org
tkou...@google.com
█ dhidalgo@google.com
zmo@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug



Sign in to add a comment

Visual corruption on new Gmail.com

Project Member Reported by ericrk@chromium.org, Apr 25 2018 
Chrome Version: 65.0.3325.181
OS: Win10

What steps will reproduce the problem?
(1) Opt in to Gmail.com redesign.
(2) Load Gmail.com in a new tab
(3) Visual corruption occurs.

This info comes from an external user (not on this bug). Only reproduced once.

It sounds like we're drawing invalid data - alternating tiles appear invalid and solid-black, creating a large checker-board pattern.

chrome:gpu and chrome:version attached - chrome:gpu has some interesting data in logs - seems like we're trying to draw with invalid textures.
version_gmail_corruption.txt
1.5 KB View Download
about_gpu_gmail_corruption.txt
18.6 KB View Download

Comment 1 by jmatias@google.com, Apr 26 2018 

This is another report, from a different user, same repro steps
about_gpu_gmail_corruption_2.txt
10.4 KB View Download
screen when updated.jpg
38.5 KB View Download

Comment 2 by jmatias@google.com, Apr 26 2018 

Both users are able to move again to classic and back to new gmail without issues after the first time.

Comment 3 by schenney@chromium.org, Apr 26 2018

Components: -Blink>Compositing

Comment 4 by zmo@chromium.org, Apr 26 2018

Labels: Restrict-View-Google
Set to Googler only in case gmail new look isn't public info yet

Comment 5 by kirish@google.com, Apr 26 2018

Labels: -Restrict-View-Google
The new gmail was launched yesterday, and this bug was filed by an external user in response to that launch.

Comment 6 by zmo@chromium.org, Apr 26 2018 

Good to know.

First, we need a reliable way to reproduce. Can we ask the affected users to opt out the gmail dogfood. Then launch Chrome with --user-data-dir=SOME_NEW_TEMP_DIR and opt in to gmail dogfood and see if they can reliably reproduce this each time?

Second, I doubt we will patch M65 again. So can we ask the affected users to test Beta (M66) and see if the issue is still there?

Comment 7 by zmo@chromium.org, Apr 26 2018 

I tried on a Win10 laptop with Intel HD 520 and no luck reproducing

Comment 8 by zmo@chromium.org, Apr 26 2018

Labels: -Pri-1 Pri-3
Just realized I am on M66 already. Both reports are on M65.

Downgrade to P3 unless we receive such reports on M66.

Comment 9 by reve...@chromium.org, Apr 27 2018

Owner: zmo@chromium.org
Status: Assigned (was: Untriaged)

Comment 10 by zmo@chromium.org, May 11 2018

Status: WontFix (was: Assigned)
It seems no new reports on M66. Closing as WontFix
►

Sign in to add a comment