Avoid SkImage ref churn in short lived SkBitmapProvider

Avoid SkImage ref churn in short lived SkBitmapProvider

SkBitmapProvider is always stack-allocated and tightly-scoped.  It
should be safe to store a SkImage rawptr instead of a ref object.

R=reed@google.com
GOLD_TRYBOT_URL= https://gold.skia.org/search?issue=2424813002

Committed: https://skia.googlesource.com/skia/+/862a3876086a9367c584598038887b94d8065fd7

[f(malita), 2016-10-17 13:30:59]

Description was changed from

==========
Avoid SkImage ref churn in short lived SkBitmapProvider

SkBitmapProvider is always stack-allocated and tightly-scoped.  It
should be safe to store a SkImage rawptr instead of a ref object.

R=reed@google.com
==========

to

==========
Avoid SkImage ref churn in short lived SkBitmapProvider

SkBitmapProvider is always stack-allocated and tightly-scoped.  It
should be safe to store a SkImage rawptr instead of a ref object.

R=reed@google.com
GOLD_TRYBOT_URL= https://gold.skia.org/search?issue=2424813002
==========

[f(malita), 2016-10-17 13:32:12]

The CQ bit was checked by fmalita@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-10-17 13:32:16]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[f(malita), 2016-10-17 13:39:35]

The CQ bit was unchecked by fmalita@chromium.org

[reed1, 2016-10-17 13:45:47]

that's wacky cool
lgtm

[f(malita), 2016-10-17 13:55:26]

The CQ bit was checked by fmalita@chromium.org

[f(malita), 2016-10-17 13:55:26]

The patchset sent to the CQ was uploaded after l-g-t-m from reed@google.com
Link to the patchset: https://codereview.chromium.org/2424813002/#ps20001
(title: "whitespace cleanup")

[commit-bot: I haz the power, 2016-10-17 13:55:41]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-10-17 14:16:11]

Description was changed from

==========
Avoid SkImage ref churn in short lived SkBitmapProvider

SkBitmapProvider is always stack-allocated and tightly-scoped.  It
should be safe to store a SkImage rawptr instead of a ref object.

R=reed@google.com
GOLD_TRYBOT_URL= https://gold.skia.org/search?issue=2424813002
==========

to

==========
Avoid SkImage ref churn in short lived SkBitmapProvider

SkBitmapProvider is always stack-allocated and tightly-scoped.  It
should be safe to store a SkImage rawptr instead of a ref object.

R=reed@google.com
GOLD_TRYBOT_URL= https://gold.skia.org/search?issue=2424813002

Committed:
https://skia.googlesource.com/skia/+/862a3876086a9367c584598038887b94d8065fd7
==========

[commit-bot: I haz the power, 2016-10-17 14:16:12]

Committed patchset #2 (id:20001) as
https://skia.googlesource.com/skia/+/862a3876086a9367c584598038887b94d8065fd7