Issue 403 in pdfium: PDF is rendered blank with PDFium and Google Chrome, rendered normally using Acrobat

[serge.settels@gmail.com via Monorail]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 403 by serge.se...@gmail.com: PDF is rendered blank with PDFium and Google Chrome, rendered normally using Acrobat
https://bugs.chromium.org/p/pdfium/issues/detail?id=403

What steps will reproduce the problem?
1. Open attached PDF, it will render blank

I am using pdfium.dll version built 29-7-2015 on Windows 10.

The problem might occur because the document is manipulated using ITextSharp 5.5.5 by my own routines to merge 2 PDF's. I cannot reproduce the problem but some documents (one out of every 1000?) render blank after that routine; it might have to do with the source PDF, but I cannot find the cause).

I hope somebody can diagnose what's wrong with this PDF so I can resolve the cause. Pdfium does not report any errors, all pages are just blank.. Opening it with Acrobat shows the document correctly.

Hope you can help?

Serge Settels

Attachments:
	97749a(1).pdf  1.4 MB

-- 
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

[serge.settels@gmail.com via Monorail]

Comment #1 on issue 403 by serge.se...@gmail.com: PDF is rendered blank with PDFium and Google Chrome, rendered normally using Acrobat
https://bugs.chromium.org/p/pdfium/issues/detail?id=403#c1

(No comment was entered for this change.)

Attachments:
	97749a(2).pdf  67.9 KB

-- 
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

[thestig@chromium.org via Monorail]

Updates:
	Status: Accepted

Comment #2 on issue 403 by the...@chromium.org: PDF is rendered blank with PDFium and Google Chrome, rendered normally using Acrobat
https://bugs.chromium.org/p/pdfium/issues/detail?id=403#c2

(No comment was entered for this change.)

-- 
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

[thes…@chromium.org via Monorail]

Updates:
Cc: we...@chromium.org

Comment #3 on issue 403 by the...@chromium.org: PDF is rendered blank with PDFium and Google Chrome, rendered normally using Acrobat
https://bugs.chromium.org/p/pdfium/issues/detail?id=403#c3

libpoppler based PDF readers display this correctly too.

Every object in the file refers to the next object. If PDFium's this is parsed recursively. The recursion limit is 30, but there are more than 30 objects, and the big image object that contains all the visible content is at the end, so the parser never gets to it.

It's not obvious if the parsing has to be recursive or not. If it does, then maybe we should raise the recursion limit. If not, then some iterative approach might be better.