Bug 696110

Summary: Broken PDF produces white pages instead of error-exit
Product: Ghostscript Reporter: ghostscript
Component: Graphics LibraryAssignee: Default assignee <ghostpdl-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: chris.liddell
Priority: P4    
Version: 9.16   
Hardware: PC   
OS: Linux   
Customer: Word Size: ---
Attachments: broken pdf

Description ghostscript 2015-07-24 04:14:45 UTC 
Created attachment 11822 [details]
broken pdf

A Document-scanner (Brother ADS-1600w) produces broken PDFs (yes, they are bad for this) and GS tries to handle them with a bad result.

Problem: pages rendered with gs are complete white. (version 9.16)

Expected: 
broken pdf fixed and rendered proper
or
broken pdf rejected and exit with an error-code.

commandline:
gs -sDEVICE=jpeg -dSTRICT -o BRW485AB67E7D88_001634-%d.jpg -f BRW485AB67E7D88_001634.pdf

Output:
GPL Ghostscript 9.16 (2015-03-30)
Copyright (C) 2015 Artifex Software, Inc.  All rights reserved.
This software comes with NO WARRANTY: see the file PUBLIC for details.
Processing pages 1 through 2.
Page 1
   **** Error reading a content stream. The page may be incomplete.
   **** File did not complete the page properly and may be damaged.
Page 2
   **** Error reading a content stream. The page may be incomplete.
   **** File did not complete the page properly and may be damaged.

   **** This file had errors that were repaired or ignored.
   **** Please notify the author of the software that produced this
   **** file that it does not conform to Adobe's published PDF
   **** specification.

> echo $?
0

Problem does not occure with GS 9.10. the pages are rendered as expected/seen in a pdf-viewer.
Comment 1 ghostscript 2015-07-24 04:23:54 UTC 
problem also does not affect GS 9.15. Images are rendered as expected, too.
Comment 2 Chris Liddell (chrisl) 2015-07-24 06:29:33 UTC 
As the current in-development code renders the file just fine, I'm going to guess it is this problem:

http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=668406a5

*** This bug has been marked as a duplicate of bug 696005 ***