[PDF] Fix memory hungry inefficiency in pdf resource tracking.
authorvandebo@chromium.org <vandebo@chromium.org@2bbb7eff-a529-9590-31e7-b0007b416f81>
Fri, 9 Mar 2012 22:16:58 +0000 (22:16 +0000)
committervandebo@chromium.org <vandebo@chromium.org@2bbb7eff-a529-9590-31e7-b0007b416f81>
Fri, 9 Mar 2012 22:16:58 +0000 (22:16 +0000)
commit188838c20818307fda770ffc395a76ea63c1c8cc
tree933be3d47fe2ec30a9a95d8b1e6cd2fc58be00cc
parenta2d8014e66cb576a25af918fb04691cc8e006b3f
[PDF] Fix memory hungry inefficiency in pdf resource tracking.

When moving the content of a device into a PDF object like SkPDFFormXObject
or SkPDFShader does, we only need the top level resources in the new object's
resource list, not the recursive set of objects.  Otherwise, when you
put a form on a form on form, etc, references to the objects multiply.

This fixed http://crbug.com/117321

Review URL: https://codereview.appspot.com/5796048

git-svn-id: http://skia.googlecode.com/svn/trunk@3360 2bbb7eff-a529-9590-31e7-b0007b416f81
include/pdf/SkPDFDevice.h
include/pdf/SkPDFPage.h
include/pdf/SkPDFTypes.h
src/pdf/SkPDFDevice.cpp
src/pdf/SkPDFFormXObject.cpp
src/pdf/SkPDFPage.cpp
src/pdf/SkPDFShader.cpp