Issue metadata
Sign in to add a comment
|
Website icon glitches on some android phones
Reported by
hexerdo...@gmail.com,
Dec 7
|
||||||||||||||||||||
Issue descriptionExample URL: https://editor.construct.net/r129/ Steps to reproduce the problem: 1. Navigate to https://editor.construct.net/r129/ 2. See Main "C" like icon glitches, black areas appear over it. What is the expected behavior? No black areas, no glitching. Website icon should load like it does on pc and some other phones What went wrong? When loading website, the website loading icon starts glitching on my android phone, but it does glitch on other phones or on pc. Also see attched video. Does it occur on multiple sites: No Is it a problem with a plugin? N/A Did this work before? N/A Does this work in other browsers? N/A Chrome version: 71.0.3578.80 Channel: stable OS Version: 7 Flash Version: I use Redmi Note 4x. MiUi Global 10.1. I also tried latest canarly, it has same glitching behavior.
,
Dec 7
,
Dec 10
,
Dec 10
Looks like out of memory GPU error, or some other raster bug. I strongly suspect it's a graphics chip issue given the inability to reproduce elsewhere.
,
Dec 10
I tried frist use chrome dev tool -> remote device to record it, but with remote device it did not happen. But with remote device it looks like it loads slower(does not refresh that icon so fast). But without any other tool it happens almost everytime, when different parts of that icons just glitch and turn black.
,
Dec 11
Tested the issue in Android and able to reproduce the issue. Steps Followed: 1. Navigated to https://editor.construct.net/r129/ 2. Observed flash of c icon Chrome versions tested: 71.0.3578.83 , 73.0.3637.0 OS: Android 7.0.0 Android Devices: Redmi 5 Using the per-revision bisect providing the bisect results, Good Build - 67.0.3364.0 Bad Build - 67.0.3365.0 CL: https://chromium.googlesource.com/chromium/src/+/1ca2fa28785179fc17ee17fe88f455ec08373930 @ fs@opera: Could you please look into the issue, pardon me if it has nothing to do with your changes and if possible please assign it to owner concerned. NOTE: Issue is not seen in Pixel devices. Thanks!
,
Dec 11
It's possible that my change exposed this issue by changing which code-path clipping will take. The issue is pretty much bound to have existed prior to my change though (which basically just flipped a flag from 'false' to 'true'), and given that it doesn't reproduce on all devices it wouldn't appear to be a Blink bug. Unassigning and moving this back to untriaged - hopefully someone of the GPU raster crowd has a better idea.
,
Dec 14
Need to determine if it's Skia or CC causing the issue, will do some triage. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by hexerdo...@gmail.com
, Dec 713.5 MB
13.5 MB View Download