Rendering corruption via JBIG2 Symbol Dictionary Cache

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Obtain two special PDF files with JBIG2 image content.
2. Render their images two separate PDFium invocations.
3. Render their images with a single PDFium invocations.

What is the expected output? What do you see instead?
Expected: Identical output from steps #2 and #3.
Actual: Step #3 misrenders the second PDF. A page ends up blank.

What version of the product are you using? On what operating system?
chromium/2510 Linux

Please provide any additional information below.
There has been extensive tracing and discussion. The JBIG2 symbol dictionary 
cache is in a static data structure that persists between the two documents. We 
observed data from the first document cause an unexpected cache hit in the 
second document. Recommend disabling the cache until this problem is fully 
understood and resolved.

Original issue reported on code.google.com by jbrei...@google.com on 1 Oct 2015 at 9:31

[GoogleCodeExporter]

Disabled for now: 
https://pdfium.googlesource.com/pdfium/+/7886d8dcf3bc9ef9b51e733d77bd3243ef32adb
8

Original comment by thestig@chromium.org on 1 Oct 2015 at 10:13

[GoogleCodeExporter]

PS. If you are thinking of working on the core problem, come talk to me first 
to save time. There is already some deep investigation.

Original comment by jbrei...@google.com on 1 Oct 2015 at 11:04

[GoogleCodeExporter]

There's internal discussion on b/24240490, where I'm CC'd as well. I have 
enough problems to work on as is. I'll leave this one to y'all.

Original comment by thestig@chromium.org on 2 Oct 2015 at 2:32

• Changed state: Accepted

[GoogleCodeExporter]

https://pdfium.googlesource.com/pdfium/+/f1b88e76134808f36f16b9e53a2e9dd89b12c8f
d

Original comment by thestig@chromium.org on 8 Oct 2015 at 9:20

• Changed state: Fixed

[GoogleCodeExporter]

Issue 93 has been merged into this issue.

Original comment by thestig@chromium.org on 8 Oct 2015 at 9:25