Issue metadata
Sign in to add a comment
|
Render problem of gpu raster on chrome 55.0.2883.91 and 56.0.2924.87
Reported by
lidasong...@gmail.com,
Feb 9 2017
|
||||||||||||||||||||||
Issue descriptionSteps to reproduce the problem: 1. Use the Redmi Note 4 Phone 2. Open a Hybrid App with chrome 55.0.2883.91 or 56.0.2924.87 3. The rendering problem will show. 4. When I down the version of webview to 53.0.2785.124, this will be solved. What is the expected behavior? Some wrong rendered images will correctly. What went wrong? Some use the 'background-image' renderd at wrong position, and Irregular. (add right and wrong screenshots) Did this work before? N/A Chrome version: 55.0.2883.91 Channel: stable OS Version: 4.0 Flash Version: Shockwave Flash 24.0 r0
,
Feb 9 2017
Issue 690279 has been merged into this issue.
,
Feb 10 2017
Thanks for your quick reply, kochi. I attached my project, you can open the index.html to see, but as the demo request to the online server, you need use a agent to deal with the cross domain problem. Or, you can also request 'http://app.mi.com/' to see it.
,
Feb 10 2017
Thanks, opening http://app.mi.com on mobile (Google Pixel here) reproduced the issue. (The URL is redirected to http://app.xiaomi.com/home ). Attached the screenshot. I took a look a bit, and found that the border line is drawn with CSS: HTML: <div class="applist-wrap"> ... </div> CSS: .applist-wrap { ... background-image: linear-gradient(180deg, transparent, transparent 67%, #d3d3d3 67%); background-size: 100% 1px; } Over to CSS team so this linear-gradient behavior is expected or not. PS I could not reproduce this with desktop Chrome with "fake" Nexus5X mode in the inspector, but I could with GalaxyS5.
,
Feb 13 2017
Thank you , kochi. What you said is the reason, but this had never happend on other devices before. So the css team will help me to check the problem?
,
Feb 13 2017
Yeah, I was just categorizing "Blink" (our renderer) problem to proper team so this issue gets in the rader of the style team.
,
Mar 2 2017
,
Mar 7 2017
looks like it's related to GPU rasterization on Mali T860/T880. Force turning off GPU raterization on those devices can workaround this issue.
,
Jul 7 2017
Based on comment #8, reassigning to GPU component.
,
Oct 18 2017
,
Oct 27 2017
ppolisetty@ Can you check if it repros on latest builds and triage accordingly?
,
Jan 4 2018
per #27, assigning to ppolisetty@
,
Jan 8 2018
I was able to repro this issue only on Nexus 5X/8.1.0 on 61.0.3163.98 & 63.0.3239.111 . However, I was unable to repro this issue on Redmi Note 4/NRD90M on both System Image:58.0.3029.83 & 63.0.3239.111, Nexus 5/MOB31V on latest 63.0.3239.111, & Galaxy S5/MMB29M on 63.0.3239.111. I have added screenshots, logcat & bugreport@ http://go/chrome-androidlogs1/6/690284
,
Jan 8 2018
Over to hcm@ for triage. It appears that this is a linear-gradient issue under GPU raster, where our rounding behavior results in a thin gradient disappearing / reappearing depending on its position.
,
Jan 10 2018
,
Jan 10 2018
I'm fairly sure this bug has been misunderstood and triaged wrong from day one. Go back and look at the original two images. Yes, there is a slight difference in the rendering of the divider lines, but there is a much more egregious error in the rendering of the stars for the first, third, and fifth apps - they're all shifted vertically (with repeat mode). None of the subsequent images posted by Chromium devs reproduce that bug.
,
Jan 10 2018
Agree with Brian now that he's pointed this out, there appear to be some larger alignment issues... Also, did we confirm with the reporter or a repro that turning off GPU raster changed this behavior?
,
Jan 11 2018
ppolisetty@, as you have the device in quesetion, can you re-confirm whether the issue repros on latest Chrome (per comment #17, with regards to the stars being corrupt, not the border lines). Also, can you try with GPU Rasterization enabled/disabled (option is in about:flags, gpu rasterizaiton). If not, let's just close this out.
,
Feb 22 2018
Closing this issue as I could not repro this issue(as mentioned in #17) on Nexus 5X/8.1.0 with the latest Chrome:64.0.3282.137 & Chrome Beta: 65.0.3325.85. I also tried with GPU Rasterization enabled/disabled on both the chrome versions and could not repro the issue. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by kochi@chromium.org
, Feb 9 2017NextAction: 2017-02-23