Set maximum output size for scaled-image-cache images

src/core/SkScaledImageCache.h

Index: src/core/SkScaledImageCache.h
diff --git a/src/core/SkScaledImageCache.h b/src/core/SkScaledImageCache.h
index fe072306d383f44eec7554724f4c3d8b94ae9fdf..48f143b204d3256f0d33a5d119cbb71c86e03681 100644
--- a/src/core/SkScaledImageCache.h
+++ b/src/core/SkScaledImageCache.h
@@ -64,6 +64,9 @@ public:
     static size_t GetByteLimit();
     static size_t SetByteLimit(size_t newLimit);
 
+    static void SetMaximumOutputSizeForHighQualityFilter(size_t);

[reed1, 2014/07/16 18:38:00]

What if we rename SetByteLimit to SetTotalByteLimit, and name the new one
SetSingleByteLimit?

I think the name should be more inline with the other names, i.e. about
allocation requests, and less about input-vs-output etc.

+    static size_t GetMaximumOutputSizeForHighQualityFilter();
+
     static SkBitmap::Allocator* GetAllocator();
 
     /**
@@ -148,6 +151,12 @@ public:
     size_t getByteLimit() const { return fByteLimit; }
 
     /**
+     *  This is respected by SkBitmapProcState::possiblyScaleImage.
+     *  0 is no maximum at all; this is the default.
+     */
+    void setMaximumOutputSizeForHighQualityFilter(size_t maximumAllocationSize);
+    size_t getMaximumOutputSizeForHighQualityFilter() const;
+    /**
      *  Set the maximum number of bytes available to this cache. If the current
      *  cache exceeds this new value, it will be purged to try to fit within
      *  this new limit.
@@ -177,6 +186,7 @@ private:
 
     size_t  fBytesUsed;
     size_t  fByteLimit;
+    size_t  fMaximumOutputSizeForHighQualityFilter;
     int     fCount;
 
     Rec* findAndLock(uint32_t generationID, SkScalar sx, SkScalar sy,