PDF with huge embedded image is displayed as a blank page

PDF: DC000933-uncompressed.pdf

If I open the above PDF in Chrome or Firefox, it is shown as blank at best. Firefox sometimes crashes if I (re)load a couple of times (even at a fresh start-up). I haven’t built Firefox with symbols, but GDB shows that the stack trace ends in mozalloc_abort, which suggets that this segfault is caused by a memory allocation error.

This PDF is quite unusual, it has a width and height with excessive values:

<< /Contents 10 0 R /MediaBox [ 0 0 4444 2592 ] /Parent 6 0 R /Resources << /ExtGState << /G0 11 0 R /G1 12 0 R /G2 13 0 R >> /ProcSet [ /ImageB /ImageC /ImageI ] /XObject << /I0 14 0 R >> >> /Type /Page >>

...

<< /BitsPerComponent 1 /ColorSpace /DeviceGray /DecodeParms << /Columns 24688 /K -1 /Rows 14400 >> /Filter /CCITTFaxDecode /Height 14400 /Name /I0 /Subtype /Image /Type /XObject /Width 24688 /Length 972551 >>

It was allegedly created by MetaPrint.

[MaRieck]

I appreciate that some movement comes into this 😃 hopefully you are able to find it @marco-c and @brendandahl .BTW: I think this “performance” label is wrong. This issue has nothing to do with performance but rather of functionality/bug in edge-cases (embedded image size too large).

[Benguenette]

Hi, I come and read here every once in a while hoping that a solution shows up. It’s been a few years now and working in engineering document management like some of the users here, It gives us a headache.

Is there an explanation why it’s still open or maybe there’s a limitation in the code making a solution impossible? It would be really appreciated.