Issue 264 in pdfium: pdfium_test on XFA branch crash on taking multiple pdf files

[zhaoqin@google.com via Monorail]

Status: Accepted
Owner: ----
CC: thes...@google.com, tse...@google.com
Labels: Type-Defect Priority-Medium OpSys-Windows DrMemory XFA

New issue 264 by zhao...@google.com: pdfium_test on XFA branch crash on
taking multiple pdf files
https://bugs.chromium.org/p/pdfium/issues/detail?id=264

bin\drmemory.exe -pause_at_error -light -fuzz_target "<main>!RenderPdf|4|1|
2|1000" -- d:\src\pdfium\out\Debug\pdfium_test.exe --png
d:\tmp\radiocheckbox_xfa.pdf

...
Rendering PDF file d:\tmp\radiocheckbox_xfa.pdf.
Rendered 1 pages.
Skipped 0 bad pages.
Rendering PDF file d:\tmp\radiocheckbox_xfa.pdf.
Exception thrown during bootstrapping


#
# Fatal error in d:\src\pdfium\v8\src\api.h, line 400
# Check failed: allow_empty_handle || that != 0.
#

It works fine on a single input.

Try natively, it crashed too:
d:\src\pdfium> d:\src\pdfium\out\Debug\pdfium_test.exe --bmp
d:\tmp\radiocheckbox_xfa.pdf d:\tmp\radiocheckbox_xfa.pdf
Rendering PDF file d:\tmp\radiocheckbox_xfa.pdf.
Rendered 1 pages.
Skipped 0 bad pages.
Rendering PDF file d:\tmp\radiocheckbox_xfa.pdf.
Exception thrown during bootstrapping


#
# Fatal error in d:\src\pdfium\v8\src\api.h, line 400
# Check failed: allow_empty_handle || that != 0.
#


--
You received this message because:
1. The project was configured to send all issue notifications to this
address

You may adjust your notification preferences at:
https://bugs.chromium.org/hosting/settings

[zhaoqin@google.com via Monorail]

Comment #1 on issue 264 by zhao...@google.com: pdfium_test on XFA branch

crash on taking multiple pdf files

https://bugs.chromium.org/p/pdfium/issues/detail?id=264#c1

(No comment was entered for this change.)

Attachments:
radiocheckbox_xfa.pdf 291 KB

[dsincl… via monorail]

Updates:
Owner: dsin...@chromium.org
Status: Fixed

Comment #2 on issue 264 by dsin...@chromium.org: pdfium_test on XFA branch crash on taking multiple pdf files
https://bugs.chromium.org/p/pdfium/issues/detail?id=264#c2

This appears to be fixed. If you're still having issues please re-open with updated repro instructions.