Bug 21841 - Crash with "Error (0): Call to Object where the object was type 2, not the expected type 1"
Summary: Crash with "Error (0): Call to Object where the object was type 2, not the ex...
Status: RESOLVED FIXED
Alias: None
Product: poppler
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: poppler-bugs
QA Contact:
URL: http://www.librelogiciel.com/software...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-20 14:00 UTC by Eric Piel
Modified: 2009-05-20 14:22 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description Eric Piel 2009-05-20 14:00:14 UTC 
Tyring to open the PDF linked in the URL, poppler crashes with this error:
Error (0): Call to Object where the object was type 2, not the expected type 1

This happens both with evince and with pdftoppm. Acrobat reader (9.0) opens this document without problem and without warning about any error.

Note also that this document was created using the F/OSS reportlab package (via PDFMap http://www.librelogiciel.com/software/PDFMap/).
Comment 1 Albert Astals Cid 2009-05-20 14:22:46 UTC 
Just fixed on master branch, anyway the PDF is wrong, has /Mask entries with real values when they should be integer values (Color Key masking section of 4.8.5 Masked Images in the PDF spec), please open a bug against the PDFMap project.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.