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

Issue 793710 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: May 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Bug



Sign in to add a comment

cc::ResourcePool::TryAcquireResourceForPartialRaster crash

Reported by zljj0...@gmail.com, Dec 11 2017

Issue description

Chrome Version       : 61.0.3163.91
OS Version: android 7.0
URLs (if applicable) :
Other browsers tested:
  Add OK or FAIL after other browsers where you have tested this issue:
     Safari:
    Firefox:
    IE/Edge:

What steps will reproduce the problem?
No stable steps

What is the expected result?
android webview do not crash


What happens instead of that?
Crash in cc::ResourcePool::TryAcquireResourceForPartialRaster:
when run in this code:
resource->invalidated_rect().size().GetArea();

Seem that tile's invalidated content rect's area is out of Integer scope, and cause abort by self.

For tile's invalid_content_rect is set by Tile::SetInvalidated, 
there are two position call this:
1. PictureLayerTiling::CreateMissingTilesInLiveTilesRect
2. PictureLayerTiling::RemoveTilesInRegion
In case 1, invalid_content_rect will intersect with tile content rect, this mean that invalidate content rect must in tile content rect;
But in case 2, invalidate content rect do not intersect with tile content rect, perhaps it set invalid value, and cause this issue;

Please confirm this.


 
@reporter:
1) Can you please upgrade your chrome to latest stable version 63.0.3239.84, you can download/install the latest chrome version stable from link: https://www.chromium.org/getting-involved/dev-channel
2) Please confirm you are checking it on Android or Linux OS and 
3) Provide the steps to reproduce the issue which helps further triaging the issue

Thanks!

Cc: viswatej...@techmahindra.com sc00335...@techmahindra.com
Labels: Needs-Milestone Needs-Feedback Triaged-ET
Components: Internals>Compositing
Status: WontFix (was: Unconfirmed)
As there is no response/Feedback from the reporter for comment#1 from long duration, hence closing this issue and marking it as Won't fix.

@Reporter: Please feel free to raise a new one if the issue is still seen.

Thanks!

Sign in to add a comment