projects / platform / upstream / libSkiaSharp.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: dc87a7d) | patch
Avoid SkImage ref churn in short lived SkBitmapProvider
authorfmalita <fmalita@chromium.org>
Mon, 17 Oct 2016 14:16:05 +0000 (07:16 -0700)
committerCommit bot <commit-bot@chromium.org>
Mon, 17 Oct 2016 14:16:05 +0000 (07:16 -0700)
commit862a3876086a9367c584598038887b94d8065fd7
tree6be6fd5e1d7ebe81ee596e8419ecea4b6a5beb68tree | snapshot
parentdc87a7d8ea51b05ba2e8d86a2665461ff641b971commit | diff
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

Review-Url: https://codereview.chromium.org/2424813002
src/core/SkBitmapProvider.h diff | blob | history
Domain: Dotnet / API;