Issue metadata
Sign in to add a comment
|
Font display issues on Android |
||||||||||||||||||||||||
Issue descriptionChrome Version: 67.0.3388.0 (Official Build) canary (32-bit) OS: Android 8.1.0; Pixel XL Build/OPM1.171019.021 What steps will reproduce the problem? (1) visit page e.g. chrome://version (2) (3) What is the expected result? Font displays right What happens instead? Fonts look weird. See screenshot. Please use labels and text to provide additional information. This is a recent regression. 411b6d4e-3f4a17df c0c84556-a48559fc 45514eb0-612a79a3 8b81f22b-3f4a17df d6f3e6fe-f23d1dea 5f419cc9-ca7d8d80 853359fa-f23d1dea 34a6bf44-ca7d8d80 da89714-4ad60575 9041608a-3f4a17df 1e528f0f-f23d1dea b130ecb8-2e32ee7e 6025934e-3f4a17df c4c991b6-3f4a17df 1949605e-502783f4 717d9da7-f23d1dea d5bf8633-c465e12f 3eb101d6-3f4a17df 8303c047-65bced95 236d5d9e-694ae69f 47e5d3db-3d47f4f4 dc462a28-5c943877 125b7f68-65bced95 c3d1d2ca-f23d1dea f15c1c09-ca7d8d80 3042ad4b-ca7d8d80 121ae2bc-ee24275d 44827ee5-43146c13 20ccf1f0-ca7d8d80 b0f37b08-65bced95 ef05a96e-47945357 9773d3bd-ca7d8d80 93731dca-e89d496c a428bf14-d532d178 889b4d5d-3f4a17df 9e5c75f1-5488fb9c 85663a5d-85634f4c f79cb77b-3f4a17df 2c45a3a5-245f619 4ea303a6-95c3cf3c b19465ab-a79d803f bcc34a89-4858ffec d92562a9-65bced95 2b33233e-881ca6c9 14c5a050-ca7d8d80 2c1d398c-3f4a17df 6973a1cf-f23d1dea 4932440-f23d1dea 1d085b67-c49ac49f 4d17cf02-ca7d8d80 247c1e6d-f23d1dea 30ab2dd8-f23d1dea c332d3b5-f23d1dea 344833e9-1525b35b 3f273a97-25a103a9 4bc337ce-69465896 494d8760-52325d43 3ac60855-3ec2a267 4442aae2-7158671e ed1d377-e1cc0f14 75f0f0a0-d7f6b13c e7e71889-e1cc0f14 6c05ec0-f23d1dea bbb8f811-f23d1dea 1e902a37-f23d1dea 493ac2c5-ca7d8d80 For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report.
,
Apr 5 2018
,
Apr 5 2018
Tested the issue in Android and able to reproduce the issue. Steps Followed: 1. Launch Chrome. 2. Navigate to chrome://version 3. Observe weird font Chrome versions tested: 67.0.3388.0(Canary) OS: Android 8.1.0 Android Devices: Pixel XL Using the per-revision bisect providing the bisect results, Good Build - 67.0.3387.0 Bad Build - 67.0.3388.0 You are looking for a change made after 547606(GOOD), but before 547607(BAD). CHANGELOG URL: The script might not always return single CL as suspect as some perf builds might get missing due to failure. https://chromium.googlesource.com/chromium/src/+/aa8304925672de76f13fcd46d49f305d98e636b6 From the CL above, assigning the issue to the owner concerned. @cnardi: 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. Please navigate to below link for log's and video-- go/chrome-androidlogs/829163 Thanks!!
,
Apr 5 2018
Fairly confident this isn't my change, all it did was change serialization via Javascript which should have no effect on rendering. Nothing strange jumped out at me from the changelog, perhaps this was actually a painting/compositing change? Maybe a re-bisect would help?
,
Apr 5 2018
This could be a canary only variation which is why it did not appear in Dev 3387. Can you rerun with wider range (verify ranges) and Finch params in #1
,
Apr 8 2018
Still happening on 67.0.3390.1 (Official Build) canary (32-bit)
,
Apr 9 2018
Retried the tool bisect with different range, still didn't get the possible suspect. (Able to get the good and bad combination in tool bisect) Unable to find the exact suspect from manual change log as well CL: https://chromium.googlesource.com/chromium/src/+log/67.0.3387.0..67.0.3388.0?pretty=fuller&n=10000 Requesting someone from Blink>Fonts team to take a look at this and help us in assigning the issue to appropriate owner. Thanks!!
,
Apr 11 2018
,
Apr 16 2018
Since this is a recent regression, tagging as RBS.
,
Apr 16 2018
This is no longer happening on my canary chrome android 67.0.3396.3
,
May 9 2018
Is this now fixed? Please update the status of this blocker as soon as possible.
,
May 9 2018
,
May 10 2018
I don't think this is a dup of 840010 and associated issues, which were a regression introduced late last week and now reverted. It does seem like this may be fixed now, however, please reopen if experiencing again.
,
May 15 2018
Thanks, hcm@, sorry if I shoved this in the wrong triage bucket. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by wfh@chromium.org
, Apr 5 2018