Summary: | Lines are missing in TIFF-output when -dBufferSpace is too large | ||
---|---|---|---|
Product: | Ghostscript | Reporter: | artifex |
Component: | Printer Driver | Assignee: | Ray Johnston <ray.johnston> |
Status: | NOTIFIED FIXED | ||
Severity: | normal | CC: | leonardo |
Priority: | P2 | ||
Version: | 9.06 | ||
Hardware: | All | ||
OS: | All | ||
Customer: | 870 | Word Size: | --- |
Attachments: |
ISO-A0.pdf
ISO-A0c.pdf |
Description
artifex
2012-12-19 14:37:43 UTC
Created attachment 9155 [details]
ISO-A0c.pdf
Simplified version of the original attachment.
You can see the difference in output using these command lines: bin/gs -sDEVICE=ppmraw -o test.ppm -r600 -dBufferSpace=50000000 ./ISO-A0c.pdf and bin/gs -sDEVICE=ppmraw -o test.ppm -r600 -dBufferSpace=10000000 ./ISO-A0c.pdf The former produces a completely blank page, the latter the expected dashed line. Assigning to Ray since this appears to be a clist issue. I'm not sure how this is a clist issue since it WORKS when the clist is used. For example: -dMaxBitmap=10000 -dBandHeight=7000 produces output matching Adobe and -Z: displays: [:]width=5100, band_width=5100, band_height=7000, nbands=1 % Start time = 0.109, memory allocated = 2274440, used = 2051025 Processing pages 1 through 1. Page 1 [:]width=2400, band_width=2400, band_height=7000, nbands=1 [:]width=2400, band_width=2400, band_height=7000, nbands=1 % Outputpage start time = 0.183, memory allocated = 2550408, used = 2366053 I'll look at it and see if I can see what's going on, and assign it to whoever is more appropriate. This is an issue with clipping. Tracing with the debugger, the clip rectangle with the clist has xmin=0x37a and xmax=0x37b. In page mode, the xmin=0x37a, but the xmax=0x37a meaning that after clipping, we fill a rectangle of 0 width. I'm looking at how the clipping box gets set now, and why it's different. *** Bug 690036 has been marked as a duplicate of this bug. *** WIth some paths, the fill_adjust was not being applied,. Testing a change to always us it when clipping. |