Issue 472813  has been merged into this issue.

 http://crbug.com/159524  was filed to unify the tile size decisions for all platforms. It got duped/fixed when we added a DSF tile size for chromeos.

Also, ganesh uses viewport-sized tiles which is terrible when windows get resized, as we recreate everything all the time.

I think we can solve all of these by making tile size a divisor of the physical screen size (different from the viewport, and more stable on desktop).

From aelias:

> Hmm, I had to look it up a bit.  Unfortunately, physical_backing_size_/device_viewport_size is not stable.
> 
> There are two reasonable ways to get a stable viewport size in physical pixels:
> 1) OutputSurface::SurfaceSize()
> 2) (viewport_size + top_controls_shrink_blink_size ? top_controls_height : 0) * device_scale_factor
> 
> I actually propose that you take the intersection (min) of those two sizes.  The reason is WebView.
> WebView can have the viewport (Android View size) either much larger or much smaller than the
> OutputSurface size (GL framebuffer size).  Taking the smaller of the two will solve  http://crbug.com/472813 
> while avoiding introducing the inverse problem for tiny WebViews.

https://codereview.chromium.org/2099903002/ is a WIP CL for this "Make tile size a function of the device scale factor."

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

This appears fixed in PictureLayerImpl.

Only for gpu raster path I think, FWIW.

Oh, quite right.