diff options
author | Tom Sepez <tsepez@chromium.org> | 2017-03-15 15:24:57 -0700 |
---|---|---|
committer | Chromium commit bot <commit-bot@chromium.org> | 2017-03-15 22:50:56 +0000 |
commit | 972eb5c6843b235e5414c86c41e962151a94870c (patch) | |
tree | ab0678b757c6da4b7d11219192eae50999f65ee9 /testing/resources/javascript/array_buffer_expected.txt | |
parent | c467d4619ebe0bae9a87b667ca9a06f576138f68 (diff) | |
download | pdfium-972eb5c6843b235e5414c86c41e962151a94870c.tar.xz |
Add array_buffer JS test.
JS Array Buffers are the first candidate to be allocated from
PartitionAlloc when it becomes available, so add test first.
Presently, we will return as large an array buffer as the system
can handle; this is generally a bad idea so limit them to 256MB
and test that we handle failure.
Change-Id: I205745a7938d69eb32ac883b90824f2f9e584ec7
Reviewed-on: https://pdfium-review.googlesource.com/3065
Reviewed-by: Lei Zhang <thestig@chromium.org>
Commit-Queue: Tom Sepez <tsepez@chromium.org>
Diffstat (limited to 'testing/resources/javascript/array_buffer_expected.txt')
-rw-r--r-- | testing/resources/javascript/array_buffer_expected.txt | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/testing/resources/javascript/array_buffer_expected.txt b/testing/resources/javascript/array_buffer_expected.txt new file mode 100644 index 0000000000..f8f3bf227c --- /dev/null +++ b/testing/resources/javascript/array_buffer_expected.txt @@ -0,0 +1,5 @@ +Alert: This test attempts to make array buffers until exhausted +Alert: Trying size 1000 +Alert: Trying size 2000000 +Alert: Trying size 4000000000 +Alert: Caught error RangeError: Array buffer allocation failed |