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

Issue 707839 link

Starred by 4 users

Issue metadata

Status: Fixed
Owner:
inactive
Closed: Apr 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug

Blocked on:
issue 670607
issue 698197



Sign in to add a comment

Graphical glitches on tablets reported on Play Store reviews

Project Member Reported by aelias@chromium.org, Apr 3 2017

Issue description

candrada@, could QA team try to reproduce on one of the specific devices mentioned ("Galaxy Tab 4", "Xperia Z3 tablet", "Lenovo TB2") on latest M57, then bisect to culprit CL?  See screenshots on https://docs.google.com/document/d/1QJhklbeZqkaorZ-ABtL0kbhA6_-Txi05K3mta5CagfI/edit.  It sounds like just switching tabs back and forth might be enough to repro.

I suspect this is GPU driver related.  It's similar to the issue that has been recurring on Nexus 7 (http://crbug.com/698197,  http://crbug.com/670607 ), but affects more devices.
 
Cc: candr...@chromium.org
Owner: kgna...@chromium.org
kgnaidu, can you try to repro the issue on the Galaxy Tab 4 10.1 that you have?  Thanks!
Able to repro the bug on Samsung Galaxy Tab4 (T530NU) / LRX22G.

Please find logs and Video @ http://go/chrome-androidlogs1/7/707839
Great, could you further get an exact bisect?
Steps to Repro: 
1.Launch chrome
2,Open few tabs with content and switch between the tabs

Observed behavior : Graphical glitches obserevd while switching between the tabs  

Bisected to few builds and Issue also reproducible on 57.0.2987.97. 
MTV can you help with further bisecting down to find the suspect. Thanks!
Owner: prashanthpola@chromium.org
Thanks Naidu.

Prashanth, can you take over with the bisecting?
 Issue 708185  has been merged into this issue.
Labels: -Needs-Bisect
Owner: aelias@chromium.org
Bisect Info:

Good build: 57.0.2950.3
Bad build: 57.0.2951.0
Regression range: https://chromium.googlesource.com/chromium/src/+log/57.0.2950.0..57.0.2951.0?pretty=fuller&n=10000

Good commit: 438079
Bad commit: 438080
Suspect CL: https://chromium.googlesource.com/chromium/src/+/acff1ef1dd7e6a0c8f162bdf71f3e5efb9b89811
Hmm, not the same bisect culprit as  http://crbug.com/670607  despite similar symptoms, but I still suspect it's the same underlying issue just masked in different ways, so I'll see if expanding https://codereview.chromium.org/2655073008 to all tablet Adreno 3xx helps (all the culprit devices are Adreno 3xx).
Project Member

Comment 9 by bugdroid1@chromium.org, Apr 6 2017

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

commit 430d8884a1783783c709bd01e544f682f5134915
Author: aelias <aelias@chromium.org>
Date: Thu Apr 06 01:57:34 2017

Scope scissor bug/MSAA/WebGL2 disabling to Adreno series.

- The scissor bug originally observed on Nexus 7 turns out to affect a swath of
Adreno 3xx tablets.  Expand it and the associated MSAA disabling to all Adreno
3xx (MSAA is already not trusted on 3xx anyway).
- Retarget the Android < 6.0 MSAA+WebGL disabling to Adreno 4xx to clarify this
entry is for is a specific remaining problem suspected to exist on certain
older 4xx drivers (not very well understood/confirmed, but kainino@ requested
this entry remain pending further investigation).
- The depth texture blacklist is ancient enough that Adreno 4xx did not exist
in those days, so target it to 2xx and 3xx series (even 3xx series may be
too new for this bug to affect it, but keeping it there for safety).

BUG= 707839 , 682075 
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel

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

[modify] https://crrev.com/430d8884a1783783c709bd01e544f682f5134915/gpu/config/gpu_driver_bug_list.json
[modify] https://crrev.com/430d8884a1783783c709bd01e544f682f5134915/gpu/config/gpu_driver_bug_list_arrays_and_structs_autogen.h
[modify] https://crrev.com/430d8884a1783783c709bd01e544f682f5134915/gpu/config/gpu_driver_bug_list_autogen.cc
[modify] https://crrev.com/430d8884a1783783c709bd01e544f682f5134915/gpu/config/software_rendering_list.json
[modify] https://crrev.com/430d8884a1783783c709bd01e544f682f5134915/gpu/config/software_rendering_list_arrays_and_structs_autogen.h
[modify] https://crrev.com/430d8884a1783783c709bd01e544f682f5134915/gpu/config/software_rendering_list_autogen.cc

Labels: Merge-Request-58
Project Member

Comment 11 by sheriffbot@chromium.org, Apr 6 2017

Labels: -Merge-Request-58 Hotlist-Merge-Approved Merge-Approved-58
Your change meets the bar and is auto-approved for M58. Please go ahead and merge the CL to branch 3029 manually. Please contact milestone owner if you have questions.
Owners: amineer@(Android), cmasso@(iOS), bhthompson@(ChromeOS), govind@(Desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Project Member

Comment 12 by bugdroid1@chromium.org, Apr 6 2017

Labels: -merge-approved-58 merge-merged-3029
The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/a80032606fb22ed36a6bd599d98bd0c13323cdd9

commit a80032606fb22ed36a6bd599d98bd0c13323cdd9
Author: Alexandre Elias <aelias@chromium.org>
Date: Thu Apr 06 19:11:55 2017

Scope scissor bug/MSAA/WebGL2 disabling to Adreno series.

[Unclean merge due to http://crrev.com/2756793003]

- The scissor bug originally observed on Nexus 7 turns out to affect a swath of
Adreno 3xx tablets.  Expand it and the associated MSAA disabling to all Adreno
3xx (MSAA is already not trusted on 3xx anyway).
- Retarget the Android < 6.0 MSAA+WebGL disabling to Adreno 4xx to clarify this
entry is for is a specific remaining problem suspected to exist on certain
older 4xx drivers (not very well understood/confirmed, but kainino@ requested
this entry remain pending further investigation).
- The depth texture blacklist is ancient enough that Adreno 4xx did not exist
in those days, so target it to 2xx and 3xx series (even 3xx series may be
too new for this bug to affect it, but keeping it there for safety).

BUG= 707839 , 682075 
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

Review-Url: https://codereview.chromium.org/2797393002
Cr-Commit-Position: refs/heads/master@{#462321}
(cherry picked from commit 430d8884a1783783c709bd01e544f682f5134915)

Review-Url: https://codereview.chromium.org/2801043004 .
Cr-Commit-Position: refs/branch-heads/3029@{#610}
Cr-Branched-From: 939b32ee5ba05c396eef3fd992822fcca9a2e262-refs/heads/master@{#454471}

[modify] https://crrev.com/a80032606fb22ed36a6bd599d98bd0c13323cdd9/gpu/config/gpu_driver_bug_list_json.cc
[modify] https://crrev.com/a80032606fb22ed36a6bd599d98bd0c13323cdd9/gpu/config/software_rendering_list_json.cc

Status: Fixed (was: Assigned)
Blockedon: 698197
Blockedon: 670607
Project Member

Comment 16 by bugdroid1@chromium.org, Apr 7 2017

 Issue 709724  has been merged into this issue.
Verified on Chrome:58.0.3029.70 Device:Samsung Galaxy Tab 4(SM-T530NU)/LRX22G

Sign in to add a comment