Blank screen on a certain device generally suggests to me a GPU or raster failure.

Not able to repro on Nexus 9/MOB31J with Latest M62 build.

Can you share what device was used for the web site?
Thanks.

Thank you for providing more feedback. Adding requester "ramine@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

Device: Acer Predator (X86_64)
Web site:  apkmirror.com

Able to repro with older chrome beta release 61.0.3113.0
Not able to repro with latest chrome stable  60.0.3112.107


No CL bisect on X86_64 devices available at this time.

Marking RBS due to high severity.  Can you please bisect to the nearest 61.0.xyz builds?

re comment 9, ramine@ bisected to those builds, it happened right around branch cut so there's no M61 build before 3113.  I tested on 60.0.3111.0 and 60.0.3112.12 (earlier builds of 60.0.3112.x crashed on start), all working fine. 

The commit range is:

https://chromium.googlesource.com/chromium/src/+log/60.0.3112.107..61.0.3113.0?pretty=fuller&n=10000

Good build: 62.0.3166.3 
Bad build:  62.0.3165.0
https://chromium.googlesource.com/chromium/src/+log/62.0.3165.0..62.0.3166.3?pretty=fuller&n=10000

There are no releases for X86_64 between the two builds.

can someone hand me that device, also what's with the two different bisect ranges..?

re c17, please come by if you still need a device.

The range in c8 indicates where the bug first occurred in M61.  The one in c14 indicates where it first went away in M62.  We'd like to get whatever fixed it in M62 into M61 before stable.

Well, the fix is https://chromium-review.googlesource.com/552837, that sounds like paint issue rather than graphics..

I guess I should figure out what the breaking change was

Issue 737317 has been merged into this issue.

bisected to skia roll: https://chromium-review.googlesource.com/517374
and then to skia commit: https://skia-review.googlesource.com/17764

the CL is *disabling* msaa on intel GPUs, which applies to this android device. but I don't really understand how that broke rendering.. usually disabling features doesn't end up breaking rendering

disable_chromium_framebuffer_multisample seem to do the trick

that already covers baytrail gpu on android. maybe should just blacklist all intel gpus instead?

This sounds like the same as  Issue 751919 .

Enabling the following workaround for "android" in /src/gpu/config/gpu_driver_bug_list.json should fix this I think:

    {
      "id": 238,
      "description": "On Intel GPUs MSAA performance is not acceptable for GPU rasterization",
      "cr_bugs": [527565, 751919],
      "os": {
        "type": "macosx"
      },
      "vendor_id": "0x8086",
      "multi_gpu_category": "any",
      "features": [
        "msaa_is_slow"
      ]
    },

ericrk@ is working on the right long term solution here: https://chromium-review.googlesource.com/c/chromium/src/+/629897

Hmm, although this should already be getting handled by...

    {
      "id": 132,
      "description": "On Intel GPUs MSAA performance is not acceptable for GPU rasterization",
      "cr_bugs": [527565],
      "vendor_id": "0x8086",
      "multi_gpu_category": "active",
      "features": [
        "msaa_is_slow"
      ]
    },

Is this workaround not triggering on Android?

vendor_id check doesn't work on android I think

I'll duplicate an entry for android..

https://chromium-review.googlesource.com/c/chromium/src/+/644610 in cq

request merge now to make into beta build tomorrow?

This bug requires manual review: We are only 5 days from stable.
Please contact the milestone owner if you have questions.
Owners: amineer@(Android), cmasso@(iOS), ketakid@(ChromeOS), govind@(Desktop)

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

Approved for M61 branch 3163.

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

commit 0bc94ae6fcabe3a5ce68972e117790f020009291
Author: Bo Liu <boliu@chromium.org>
Date: Thu Aug 31 00:01:22 2017

[Merge m61] gpu: Duplicate msaa_is_slow for intel for android

vendor_id filed does not work on android.

TBR=vmiura@chromium.org

Bug:  759471 
Change-Id: I2321486ad99e061665f1d1da4d045846803cfb01
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
Reviewed-on: https://chromium-review.googlesource.com/644686
Reviewed-by: Bo <boliu@chromium.org>
Cr-Commit-Position: refs/branch-heads/3163@{#1019}
Cr-Branched-From: ff259bab28b35d242e10186cd63af7ed404fae0d-refs/heads/master@{#488528}
[modify] https://crrev.com/0bc94ae6fcabe3a5ce68972e117790f020009291/gpu/config/gpu_driver_bug_list.json

Marking as fixed given that we're fixed in trunk / branch, but re-open if I'm wrong and more work is required.

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

commit 91809a293d3ff352068daa1a7e09082fb8106d6e
Author: Bo Liu <boliu@chromium.org>
Date: Thu Aug 31 01:28:51 2017

gpu: Duplicate msaa_is_slow for intel for android

vendor_id filed does not work on android.

Bug:  759471 
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: Id47c49dc6df852e42222c254eb0d4e7a5b317feb
Reviewed-on: https://chromium-review.googlesource.com/644610
Commit-Queue: Bo <boliu@chromium.org>
Reviewed-by: Victor Miura <vmiura@chromium.org>
Cr-Commit-Position: refs/heads/master@{#498709}
[modify] https://crrev.com/91809a293d3ff352068daa1a7e09082fb8106d6e/gpu/config/gpu_driver_bug_list.json

Verified the fix in '61.0.3163.79' release.

63.0.3214.0 contains this fix already. if you are still seeing black screen, it's likely a different issue. file a new bug please: https://goo.gl/9qkbdn

Using Acer Predator(D810) which is x86_64 tablet. I was able to repro on earlier builds as per comment 8.

baytrail has been blacklisted long ago: https://cs.chromium.org/chromium/src/gpu/config/gpu_driver_bug_list.json?rcl=e59972ccafc8c73a793bf725a2eeedf54825d50e&l=783

Device: Acer Predator X86_64/LMY47i
Website visited 'www.apkmirror.com'
blackscreen issue is not reproducible on three tested chrome builds.

Chrome Stable: 61.0.3163.83
Chrome Dev:    62.0.3202.19 
Chrome Canary: 63.0.3214.0 

 Issue 766247  has been merged into this issue.

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

commit 0036296a1128ac9cbefeaff51c8df831ec421c36
Author: Bo Liu <boliu@chromium.org>
Date: Mon Sep 18 20:36:42 2017

android: Expand msaa_is_slow intel blacklist

To cover more intel vendor names

Bug:  759471 
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: If0936786928bfa432b6bbed562cee1b4324ff622
Reviewed-on: https://chromium-review.googlesource.com/671690
Reviewed-by: Zhenyao Mo <zmo@chromium.org>
Commit-Queue: Bo <boliu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#502663}
[modify] https://crrev.com/0036296a1128ac9cbefeaff51c8df831ec421c36/gpu/config/gpu_driver_bug_list.json

Merge approved for M62 branch 3202.

And approved for M61 branch 3163 as well.

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

commit 3987c24e9cde81350ce14e287415f666865c1d28
Author: Bo Liu <boliu@chromium.org>
Date: Mon Sep 18 21:18:57 2017

[Merge M61] android: Expand msaa_is_slow intel blacklist

To cover more intel vendor names

Bug:  759471 
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: I032a87acdd3e4274df9edcfe1c11715dc12cddfb
Reviewed-on: https://chromium-review.googlesource.com/671193
Reviewed-by: Bo <boliu@chromium.org>
Cr-Commit-Position: refs/branch-heads/3163@{#1225}
Cr-Branched-From: ff259bab28b35d242e10186cd63af7ed404fae0d-refs/heads/master@{#488528}
[modify] https://crrev.com/3987c24e9cde81350ce14e287415f666865c1d28/gpu/config/gpu_driver_bug_list.json

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

commit 46d7282ec9099b55e5bc329a1845b9a1673c6e0c
Author: Bo Liu <boliu@chromium.org>
Date: Mon Sep 18 21:19:33 2017

[Merge M62] android: Expand msaa_is_slow intel blacklist

To cover more intel vendor names

Bug:  759471 
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: If0936786928bfa432b6bbed562cee1b4324ff622
Reviewed-on: https://chromium-review.googlesource.com/671690
Reviewed-by: Zhenyao Mo <zmo@chromium.org>
Commit-Queue: Bo <boliu@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#502663}(cherry picked from commit 0036296a1128ac9cbefeaff51c8df831ec421c36)
Reviewed-on: https://chromium-review.googlesource.com/671528
Reviewed-by: Bo <boliu@chromium.org>
Cr-Commit-Position: refs/branch-heads/3202@{#306}
Cr-Branched-From: fa6a5d87adff761bc16afc5498c3f5944c1daa68-refs/heads/master@{#499098}
[modify] https://crrev.com/46d7282ec9099b55e5bc329a1845b9a1673c6e0c/gpu/config/gpu_driver_bug_list.json

To be verified by the test team tomorrow

 Issue 443517 

Verified Fix for 'apkmirror.com black screen issue on Acer Predator X86_64 device with '61.0.3163.98' build.

Verified Fix on chrome beta 62.0.3202.29 on Acer(X86_64)

Verified on Chrome Dev build '63.0.3219.0' on Acer (X86_64) device.