Please find logs and Video @ http://go/chrome-androidlogs1/6/670607

Bisect script pointed to https://chromium.googlesource.com/chromium/src/+/db79085ae904b4b9f9c24f1c5ae26f9de83ae750

trchen@, Can you please look in to this, Thanks!

Issue 670639 has been merged into this issue.

kyeole / kgnaidu - Does this still repro?

This issue is still reproducible on latest M-57.0.2987.8 with below mentioned steps,

1. Launch Chrome.
2. Go to any site or google search anything in two tabs.
3. Switch between two tabs 4-5 times> Observe tab corruption appears while switching between tabs.

URGENT - PLEASE REVIEW ASAP

Greetings from the release team!

This bug is marked as an M-57 beta blocker, which means it needs to be fixed on trunk by THIS FRIDAY, Jan 27 in order to be merged back to the M57 branch on time.  Please prioritize fixing this issue.

Unsure if this bug should block the beta release, or know it should block but you won't be able to fix it in time?  CC me to this bug and we can discuss.

If you're absolutely sure this should not block beta, the bug can be punted to stable (by changing ReleaseBlock-Beta to ReleaseBlock-Stable), or if the bug should not block the release at all simply remove the release block tag.

Thanks,
Alex

It looks very similar to the Qualcomm FBO/scissor bug we had a few years ago.

I tried a few workarounds yesterday and confirmed if we skip resetting scissor rect in GLRenderer::BeginDrawingFrame, the problem goes away. I haven't figured out how the bug works exactly. It could be another manifestation of the driver bug, or it could be a bug in our command buffer workarounds. Investigation continues.

Downgrading to stable blocker because it only affects one single device.  (I know from past experience that Nexus 7 2013 has flicker bugs that affect no other Qualcomm device, so I don't think it should be more widespread.)

Investigation done. Fix pending: https://codereview.chromium.org/2655073008/

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

commit 1870af92713b4c2eefd45312b7cf9c5c18477f59
Author: trchen <trchen@chromium.org>
Date: Sat Jan 28 03:12:23 2017

[gpu/GLES2DecoderImpl] Force updating scissor state on Nexus 7 gen.2

Nexus 7 gen.2 shipped with some buggy GPU driver that can have stale
scissor state after switching current framebuffer to FBO0.

The theory is that FBO0 keeps some internal (in HW regs maybe?) scissor test
state, but the driver forgets to update it with GL_SCISSOR_TEST when FBO0 gets
bound. (So it stuck with whatever state we last switched from it.)

Also the state could stuck even if we explicitly set GL_SCISSOR_TEST again
after switching to FBO0, because the driver early exits if the new
GL_SCISSOR_TEST value matches the old one.

This CL add a workaround in GLES2DecoderImpl to shake up the scissor state
whenever we just switched to FBO0.

BUG= 670607 
CQ_INCLUDE_TRYBOTS=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/2655073008
Cr-Commit-Position: refs/heads/master@{#446894}

[modify] https://crrev.com/1870af92713b4c2eefd45312b7cf9c5c18477f59/gpu/command_buffer/service/gles2_cmd_decoder.cc
[modify] https://crrev.com/1870af92713b4c2eefd45312b7cf9c5c18477f59/gpu/config/gpu_driver_bug_list_json.cc
[modify] https://crrev.com/1870af92713b4c2eefd45312b7cf9c5c18477f59/gpu/config/gpu_driver_bug_workaround_type.h

Your change meets the bar and is auto-approved for M57. Please go ahead and merge the CL to branch 2987 manually. Please contact milestone owner if you have questions.
Owners: amineer@(clank), cmasso@(bling), ketakid@(cros), govind@(desktop)

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

This issue has been approved for a merge. Please merge the fix to any appropriate branches as soon as possible!

If all merges have been completed, please remove any remaining Merge-Approved labels from this issue.

Thanks for your time! To disable nags, add the Disable-Nags label.

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

Hmm somehow bugdroid missed the commit. It's in.

Cr-Commit-Position: refs/branch-heads/2987@{#203}

This issue is fixed on latest M-57.0.2987.52 & M-58.0.3012.0