aboutsummaryrefslogtreecommitdiffhomepage
path: root/resources
diff options
context:
space:
mode:
authorGravatar Leon Scroggins III <scroggo@google.com>2017-02-24 15:33:24 -0500
committerGravatar Skia Commit-Bot <skia-commit-bot@chromium.org>2017-02-24 21:25:44 +0000
commit0354c62e0bb89607a29ce2150e77e3308a795cc4 (patch)
treed2a93f2b6e6a6db51422ae1b69d5661bc4a0573a /resources
parentc5eabe7d22834189c77fe95ebaf72fed0ef2bb8e (diff)
Set a limit on the size for BMP images
This limit matches the limit used by Chromium. I am not aware of any real world BMPs that are larger than this (or even close to it), but there are some invalid BMPs that are larger than this, leading to crashes when we try to read a row. BUG:34778578 BUG=skia:3617 Change-Id: I0f662e8d0d7bc0b084e86d0c9288b831e1b296d7 Reviewed-on: https://skia-review.googlesource.com/8966 Reviewed-by: Matt Sarett <msarett@google.com> Commit-Queue: Leon Scroggins <scroggo@google.com>
Diffstat (limited to 'resources')
-rw-r--r--resources/invalid_images/b34778578.bmpbin0 -> 132 bytes
1 files changed, 0 insertions, 0 deletions
diff --git a/resources/invalid_images/b34778578.bmp b/resources/invalid_images/b34778578.bmp
new file mode 100644
index 0000000000..4a08a61e01
--- /dev/null
+++ b/resources/invalid_images/b34778578.bmp
Binary files differ