Bug 693447 - Non-deterministic tiffsep output under certain circumstances
Summary: Non-deterministic tiffsep output under certain circumstances
Status: RESOLVED FIXED
Alias: None
Product: Ghostscript
Classification: Unclassified
Component: Other Driver (show other bugs)
Version: master
Hardware: PC Linux
: P4 normal
Assignee: Michael Vrhel
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-13 20:43 UTC by Jason Giglio
Modified: 2019-02-01 21:52 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 2012-11-13 20:43:57 UTC 
Created attachment 9082 [details]
Test PDF 1

When outputting the attached files which are the same other than colorant naming, sometimes there are regressions in the outputted tiffs and sometimes there are not.  It appears to be a non-deterministic bug of some sort.

gsc -dNOPAUSE -dBATCH -sDEVICE=tiffsep -sOutputFile=/tmp/test1/files -f original.pdf
gsc -dNOPAUSE -dBATCH -sDEVICE=tiffsep -sOutputFile=/tmp/test2/files -f renamed.pdf


Then for each separation and the RGB:

tiffcmp /tmp/test1/files  /tmp/test2/files | grep -v "DateTime"
Comment 1 Jason Giglio 2012-11-13 20:44:14 UTC 
Created attachment 9083 [details]
Test PDF 2
Comment 2 Alex Cherepanov 2012-11-14 04:59:12 UTC 
Valgrind reports many warnings starting with:

Conditional jump or move depends on uninitialised value(s)
gsicc_get_link (gsicc_cache.c:590)
gx_concretize_ICC (gsicc.c:524)
gx_concretize_Separation (gscsepr.c:389)
gx_default_remap_color (gxcmap.c:600)
gx_remap_Separation (gscsepr.c:302)
capture_spot_equivalent_cmyk_colors (gsequivc.c:515)
update_Separation_spot_equivalent_cmyk_colors (gsequivc.c:145)
update_spot_equivalent_cmyk_colors (gsequivc.c:311)
tiffsep_update_spot_equivalent_colors (gdevtsep.c:850)
gx_install_Separation (gscsepr.c:136)
gs_setcolorspace_only (gscolor2.c:46)
gs_setcolorspace (gscolor2.c:64)
Comment 3 Michael Vrhel 2019-02-01 21:52:02 UTC 
This no longer shows any valgrind issues.