New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 832810 link

Starred by 2 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Investigate why GrContext need to be reset in ScopedGpuRaster::BeginGpuRaster

Project Member Reported by junov@chromium.org, Apr 13 2018

Issue description

ScopedGpuRaster::BeginGpuRaster needs to reset the GrContext state to avoid rendering glitches.  These glitches happen in Android WebView on pages with videa element. For example, see issue 826636

This reset should not be necessary. Must find out why they are in order to find a better solution.
 

Comment 1 by danakj@chromium.org, Apr 16 2018

Status: Assigned (was: Untriaged)

Comment 2 by rog...@vewd.com, May 29 2018

Cc: rog...@vewd.com
@Justin: You might want to check out  https://crbug.com/847348 , I'm (wildly) guessing that it could have something to do with the mysterious rendering glitches you've been hunting.

In our downstream product we got similar blocky text as shown in the gif-animation here, although all our text was blocky all the time:
https://bugs.chromium.org/p/chromium/issues/detail?id=823209#c8.

The blocky text we got was due to wrong parsing of floats in Angle when using non en_US locale. We also use --in-process-gpu which I *think* Android WebView also use?

Comment 3 by junov@chromium.org, May 29 2018

Thanks for the tip.  We can try removing the the state reset once that is fixed.
Owner: ----
Status: Available (was: Assigned)

Sign in to add a comment