Roll src/third_party/pdfium/ 6453a67d8..b242943f5 (2 commits)

https://pdfium.googlesource.com/pdfium.git/+log/6453a67d84dc..b242943f5e94

$ git log 6453a67d8..b242943f5 --date=short --no-merges --format='%ad %ae %s'
2018-04-24 dsinclair Remove m_CurNodeType from CFX_XMLParser
2018-04-24 rharrison Switch declaration order to prevent UAF

Created with:
  roll-dep src/third_party/pdfium
BUG=chromium:808333


The AutoRoll server is located here: https://pdfium-roll.skia.org

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


TBR=dsinclair@chromium.org

Change-Id: Ica15741534c4ee7dcc743f8715fb0271a1dae843
Reviewed-on: https://chromium-review.googlesource.com/1026525Reviewed-by: default avatarpdfium-chromium-autoroll <pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: pdfium-chromium-autoroll <pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#553368}
parent 2a489401
...@@ -114,7 +114,7 @@ vars = { ...@@ -114,7 +114,7 @@ vars = {
# Three lines of non-changing comments so that # Three lines of non-changing comments so that
# the commit queue can handle CLs rolling PDFium # the commit queue can handle CLs rolling PDFium
# and whatever else without interference from each other. # and whatever else without interference from each other.
'pdfium_revision': '6453a67d84dc321a5f28728e04929dc2ff35ff88', 'pdfium_revision': 'b242943f5e949ce3d92dcb62c7497815ccd231d1',
# Three lines of non-changing comments so that # Three lines of non-changing comments so that
# the commit queue can handle CLs rolling openmax_dl # the commit queue can handle CLs rolling openmax_dl
# and whatever else without interference from each other. # and whatever else without interference from each other.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment