candrada@, can you arrange to review this feedback?  It's for the M61 stable rollout, so time sensitive.

prashanthpola@ is trying to repro.

we are not able to repro the issue on Chrome:61.0.3163.98 Devices:Samsung Galaxy J7(SM-J710MN)/NRD90M,Samsung Galaxy A7(SM-A700F)/MMB29K,Sony Xperia Z3(D5803)/6.0.1 tried two different languages Russian,Italian with the links below
https://www.kombispel.se/
http://www.liberoquotidiano.it/news/politica/13245981/laura-boldrini-dipendenti-della-camera-in-rivolta-denunce-contro-la-circolare.html
https://www.drive2.ru/

(1) In this report, user summarized issues in "Yahoo answer" & "Badoo"
https://listnr.corp.google.com/report/74157885708

(2) Below are additional new reports:
https://listnr.corp.google.com/report/74212190451
https://listnr.corp.google.com/report/74158493442

candrada@, Can we please adjust the milestone labels if we are still tracking this issue?

Thank you!

I was able to repro this bug on M61 Stable and M62 as well on Sony Xperia M4 Aqua / 5.0

Bisect info:
Good build: 61.0.3125.5
Bad build: 61.0.3126.0
Regression range: https://chromium.googlesource.com/chromium/src/+log/61.0.3125.5..61.0.3126.0?pretty=fuller&n=10000

Good commit: 478398
Bad commit: 478399
Culprit CL: https://chromium.googlesource.com/chromium/src/+/10b29d38bbd2eb90d7d93fb07214d468f7af7dde

Adding M63 RBS for getting it fixed soon.

askatte: Could you send the about:gpu for that device please?

This would happen if workaround 116 took effect but workaround 231 did not. But I don't think that's possible.

If this is just another variant of the driver bug for which this workaround isn't effective, maybe we should just turn disable_chromium_framebuffer_multisample back on for workaround 116.

Workaround 116:
https://cs.chromium.org/chromium/src/gpu/config/gpu_driver_bug_list.json?rcl=61.0.3126.0&l=1054

askatte: Actually I don't need you to send me the about:gpu, I'd like to just check out the device from the cabinet if I can.

Sure, you can borrow it. I have the device at my desk right now.

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

commit 2b771f55fa98a9f544424cc941cd977c9245c961
Author: Kai Ninomiya <kainino@chromium.org>
Date: Thu Oct 19 01:19:12 2017

disable_chromium_framebuffer_multisample on old Qualcomm drivers

Specifically this bug was seen on Adreno 405 on Lollipop. It turns out
that the older driver has a bug that's not covered by the fix in
https://crrev.com/c/520883 . Since this is such an old device it's not
worth it to find a workaround, instead we just re-disable multisampling
and WebGL 2.0 which were enabled in that patch.

Bug:  767913 
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
Change-Id: I661c974a617bec35eeb830fd1dffd28c0be5f7f2
Reviewed-on: https://chromium-review.googlesource.com/727182
Reviewed-by: Zhenyao Mo <zmo@chromium.org>
Commit-Queue: Kai Ninomiya <kainino@chromium.org>
Cr-Commit-Position: refs/heads/master@{#509958}
[modify] https://crrev.com/2b771f55fa98a9f544424cc941cd977c9245c961/gpu/config/gpu_driver_bug_list.json
[modify] https://crrev.com/2b771f55fa98a9f544424cc941cd977c9245c961/gpu/config/software_rendering_list.json

Merge request to M63 for #11, which is a change to GPU blacklist entries.

(Assuming we can't merge to M62, but if we can, let me know.)

Your change meets the bar and is auto-approved for M63. Please go ahead and merge the CL to branch 3239 manually. Please contact milestone owner if you have questions.
Owners: cmasso@(Android), cmasso@(iOS), gkihumba@(ChromeOS), govind@(Desktop)

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

askatte@, please check this in M64.

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

commit 3d4aa1351d4f97127c04acff31438e3842c89aba
Author: Kai Ninomiya <kainino@chromium.org>
Date: Fri Oct 20 18:08:12 2017

disable_chromium_framebuffer_multisample on old Qualcomm drivers

Specifically this bug was seen on Adreno 405 on Lollipop. It turns out
that the older driver has a bug that's not covered by the fix in
https://crrev.com/c/520883 . Since this is such an old device it's not
worth it to find a workaround, instead we just re-disable multisampling
and WebGL 2.0 which were enabled in that patch.

TBR=kainino@chromium.org

Bug:  767913 
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
Change-Id: I661c974a617bec35eeb830fd1dffd28c0be5f7f2
Reviewed-on: https://chromium-review.googlesource.com/727182
Reviewed-by: Zhenyao Mo <zmo@chromium.org>
Commit-Queue: Kai Ninomiya <kainino@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#509958}(cherry picked from commit 2b771f55fa98a9f544424cc941cd977c9245c961)
Reviewed-on: https://chromium-review.googlesource.com/731005
Reviewed-by: Kai Ninomiya <kainino@chromium.org>
Cr-Commit-Position: refs/branch-heads/3239@{#114}
Cr-Branched-From: adb61db19020ed8ecee5e91b1a0ea4c924ae2988-refs/heads/master@{#508578}
[modify] https://crrev.com/3d4aa1351d4f97127c04acff31438e3842c89aba/gpu/config/gpu_driver_bug_list.json
[modify] https://crrev.com/3d4aa1351d4f97127c04acff31438e3842c89aba/gpu/config/software_rendering_list.json

Verified that there are no black patches or complete black screen on sites like nytimes.com or live.vodafone.de with 64.0.3245.0.

But there is lot for graphical corruption seen when navigating to any URL now. I will file a different bug for it. I don't see that issue in M61 where this bug repros.

Very strange. I didn't notice that when I was testing my patch but maybe I just wasn't looking carefully.

In any case I don't think it could be a direct result of this patch, because it was essentially a revert of https://crrev.com/c/520883 for this device. However it is possible that there's a problem with both workarounds applied at the same time.

Filed issue 776959 for the graphical corruption. Correction, its not a regression with the fix here. It repros only when 'Chrome home' is enabled.

Okay, if it's not a regression here I'll close this.

Verified fix in M63 - 63.0.3239.17. Thanks!

 Issue 781679  has been merged into this issue.