Bug 99768 - Internal Error (0): Call to Object where the object was type 7, not the expected type 9
Summary: Internal Error (0): Call to Object where the object was type 7, not the expec...
Status: RESOLVED FIXED
Alias: None
Product: poppler
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: poppler-bugs
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-02-10 23:50 UTC by Tavis Ormandy
Modified: 2017-02-13 00:16 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
Internal Error (11.23 MB, application/pdf)
2017-02-10 23:50 UTC, Tavis Ormandy 		Details
View All

Description Tavis Ormandy 2017-02-10 23:50:26 UTC 
Created attachment 129499 [details]
Internal Error

Attached scanned document causes an abort(), it works okay with ghostscript.

#0  0x00007ffff71e1c37 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1  0x00007ffff71e5028 in __GI_abort () at abort.c:89
#2  0x00007ffff79b1ba7 in Object::getRef (this=0x7fffffffd6e0) at Object.h:220
#3  0x00007ffff7a3e8e2 in OCGs::OCGs (this=0x6362a0, ocgObject=0x7fffffffd770, xref=0x6369b0) at OptionalContent.cc:67
#4  0x00007ffff79b7df1 in Catalog::Catalog (this=0x640b90, docA=0x635db0) at Catalog.cc:129
#5  0x00007ffff7a469eb in PDFDoc::setup (this=0x635db0, ownerPassword=0x0, userPassword=0x0) at PDFDoc.cc:285
#6  0x00007ffff7a46677 in PDFDoc::PDFDoc (this=0x635db0, fileNameA=0x635cc0, ownerPassword=0x0, userPassword=0x0, guiDataA=0x0) at PDFDoc.cc:169
#7  0x00007ffff7a3cae5 in LocalPDFDocBuilder::buildPDFDoc (this=0x635d90, uri=..., ownerPassword=0x0, userPassword=0x0, guiDataA=0x0) at LocalPDFDocBuilder.cc:31
#8  0x00007ffff7a4ff47 in PDFDocFactory::createPDFDoc (this=0x7fffffffd960, uri=..., ownerPassword=0x0, userPassword=0x0, guiDataA=0x0) at PDFDocFactory.cc:58
Comment 1 Albert Astals Cid 2017-02-13 00:16:21 UTC 
Fixed, thanks for the report.

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.