-
Notifications
You must be signed in to change notification settings - Fork 510
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fatal crash calling page.getPixmap() with certain pdf file pages #605
Comments
I don't know why you see no information, but those PDFs do contain errors, which also are revealed when subjecting them to e.g. |
Found the point where an issue is generated. |
what the hell - here is a pre-version: |
Thank you. |
resolved in 1.17.6 |
Please provide all mandatory information!
In some pages of certain pdf files the getPixmap crashes without showing any nformatio.
You could use these files from the IMF:
https://www.imf.org/~/media/Websites/IMF/imported-flagship-issues/external/pubs/ft/weo/2013/01/pdf/_c1pdf.ashx
https://www.imf.org/~/media/Websites/IMF/imported-flagship-issues/external/pubs/ft/weo/2013/01/pdf/_c3pdf.ashx
to reproduce the crash
Describe the bug (mandatory)
The _c1pdf.pdf file crashes when processig page 1 and the _c3pdf.pdf file crashes processing page 2 (starting from page 0).
To Reproduce (mandatory)
Step 1) Open the file with fitz.open
Step 2) Using a bucle to call getPixmap for every doc Page
Step 2.a) The specific parameters used where mat = fitz.Matrix(2.0, 2.0) and alpha=False, but the getPixmap crashes even with the default parrameters: getPixmap() and not only with getPixmap(mat,alpha=False)
Expected behavior (optional)
Getting the pixmap or a Exception
Your configuration (mandatory)
The output of
print(sys.version, "\n", sys.platform, "\n", fitz.__doc__)
:3.6.3 (v3.6.3:2c5fed8, Oct 3 2017, 18:11:49) [MSC v.1900 64 bit (AMD64)]
win32
PyMuPDF 1.17.5: Python bindings for the MuPDF 1.17.0 library.
Version date: 2020-08-06 06:31:06.
Built for Python 3.6 on win32 (64-bit).
The text was updated successfully, but these errors were encountered: