Roll PDFium.

Roll PDFium.

This brings in:

b3a788e  Fix GN PDFium build when building all.
f8af677  Always use the FreeType headers included in PDFium.
7dc63e6  Fix heap buffer overflow in CPDF_SampledFunc::v_Call
dc8c950  Don't export any OpenJPEG methods from PDFium.
71c24b8  Use system FreeType on Linux.
b38a900  Track formhandles in EmbedderTest class itself
14b2bb0  Fix infinite recursion in CPDF_RenderStatus::RenderSingleObject().
1d43e82  Add minimized test cases for stack exhaustion crash to repository.
cedc562  Merge to Master: Add output scale factor command line parameter to pdfium_test.
90f9e61  Merge to Master: Cover fpdftext.h API with embeddertests.
506e6dc  Add embedder test for stream length beyond end of file.

TBR=tsepez

Committed: https://crrev.com/dca0c18ebf3150f46c3e3d9be73a387d0f34ccc7
Cr-Commit-Position: refs/heads/master@{#314099}

[jam, 2015-01-31 01:19:24]

jam@chromium.org changed reviewers:
+ tsepez@chromium.org

[jam, 2015-01-31 01:29:39]

hmm there are some issues on trybots, I'll fix that and let you know.

[jam, 2015-01-31 02:47:32]

hmm this is failing compile on bots but passing locally. the reason is that
locally the freetype headers are in /usr/include/freetype2/. on the trybots,
they're in  /usr/include/freetype2/freetype/.

If this code was in the chromium repo, I'd depend on
"build/linux/system.gyp:freetype". However I can't do that because it would
break the standalone build. So should I remove the /usr/include/freetype part
and change it to '<!@(<(pkg-config) --cflags freetype2)', under cflags? Or
should I just use the headers that are part of freetype that's in pdfium since
we have them anyways for all platforms? I don't know what's the more correct
solution here.

[brettw, 2015-01-31 03:36:29]

brettw@chromium.org changed reviewers:
+ brettw@chromium.org

[brettw, 2015-01-31 03:36:30]

If you have the headers, I don't see anything wrong with just using them.

You can do the pkgconfig thing, but I think that should only be for the
standalone build. It's kind of slow so doing it unnecessarily in the Chrome
build isn't so great.

[jam, 2015-02-01 19:25:26]

The CQ bit was checked by jam@chromium.org

[commit-bot: I haz the power, 2015-02-01 19:26:11]

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

[commit-bot: I haz the power, 2015-02-01 19:31:33]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-02-01 19:31:33]

Try jobs failed on following builders:
  linux_chromium_gn_rel on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[jam, 2015-02-02 00:20:56]

The CQ bit was checked by jam@chromium.org

[commit-bot: I haz the power, 2015-02-02 00:21:32]

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

[commit-bot: I haz the power, 2015-02-02 01:42:57]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2015-02-02 01:43:45]

Patchset 3 (id:??) landed as
https://crrev.com/dca0c18ebf3150f46c3e3d9be73a387d0f34ccc7
Cr-Commit-Position: refs/heads/master@{#314099}

[jam, 2015-02-02 02:20:51]

Patchset #4 (id:60001) has been deleted

[Tom Sepez, 2015-08-14 22:32:34]

lgtm