Bug 694372 - Test file that seems to render with 15GB+ temp files
Summary: Test file that seems to render with 15GB+ temp files
Status: RESOLVED FIXED
Alias: None
Product: Ghostscript
Classification: Unclassified
Component: PDF Interpreter (show other bugs)
Version: master
Hardware: PC Linux
: P4 normal
Assignee: Ray Johnston
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-24 21:28 UTC by Jason Giglio
Modified: 2020-12-05 16:56 UTC (History)
1 user (show)

See Also:
Customer:
Word Size: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jason Giglio 2013-06-24 21:28:42 UTC 
I'm not sure if this is technically a GS bug, but we have some files that render with massive temp file and memory usage.  Attached is an example.

gsc -dBATCH -dNOPAUSE -dUseCropBox -sDEVICE=tiffsep -sOutputFile=/tmp/18108-buildtiffs -r300 -f 20196MOT201.pdf
Comment 1 Jason Giglio 2013-06-24 21:29:07 UTC 
Created attachment 10015 [details]
file that demonstrates bug
Comment 2 Ken Sharp 2013-06-25 08:04:38 UTC 
The file has a very large page size (~19x6 inches), its 'mostly' composed of images (850 of then) in an unreasonably large number of colour spaces (749). Although it has ExtGStates containing CA and Blend, these don't appear to actually have any transparent content.

There are also a number of shading dictionaries, again in complex colour spaces (NChannel/ICCBased)

Assuming that the large temp files are due to the clist, I'm assigning this one to Ray to have a quick look at it. I suspect that there is no actual problem, its just a consequence of the way the file is constructed.
Comment 3 Ray Johnston 2020-12-05 16:56:44 UTC 
Fixed, not sure how since git bisect first shows it fixed with
  6948650efd3fb9e2a70b8cf16aca57e9d0b7eb0a Commit of build_consolidation branch
which touches pretty much everything, and was not supposed to introduce any
functional differences.

Closing as FIXED.