Lower SkPictureShader tile size limits

Lower SkPictureShader tile size limits

Let's drop this to 4M pixels - maybe it will help relieve DM pressure on
mobile devices.

R=reed@google.com,mtklein@google.com
BUG=462348
Committed: https://skia.googlesource.com/skia/+/511005b2ccf060bd8ca5f078f2c0c7c7da5cc084

[reed1, 2015-03-13 13:10:01]

I wonder if there is an existing way to know what the embedding client's idea of
"too big" is.

We do have a max-single-alloc notion in SkResourceCache. I wonder if that value
and this should be synchronized...?

[reed1, 2015-03-13 13:10:13]

I'm also fine with a quick change too. lgtm

[f(malita), 2015-03-13 13:42:53]

On 2015/03/13 13:10:01, reed1 wrote:
> I wonder if there is an existing way to know what the embedding client's idea
of
> "too big" is.
> 
> We do have a max-single-alloc notion in SkResourceCache. I wonder if that
value
> and this should be synchronized...?

SkGraphics::SetResourceCacheSingleAllocationByteLimit()? I guess we could do
that, although I see RenderThreadImpl is setting that to 64 * 1024 * 1024 which
seems roughly equivalent to the current 16M pixels limit.

This is just a shot in the dark though - it's completely unclear whether
SkPictureShader has anything to do with the reported crashes or it just happens
to show up in stack dumps as the OOM lottery winner.

Luckily reveman mentioned ToT (M42 too?) has a much improved DM impl and we
shouldn't be seeing such crashes anymore. Probably still worth a try for M41
though.

[f(malita), 2015-03-13 13:45:34]

The CQ bit was checked by fmalita@chromium.org

[commit-bot: I haz the power, 2015-03-13 13:45:42]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/998423004/1

[commit-bot: I haz the power, 2015-03-13 13:50:48]

Committed patchset #1 (id:1) as
https://skia.googlesource.com/skia/+/511005b2ccf060bd8ca5f078f2c0c7c7da5cc084