[gs-bugs] [Bug 692663] Incorrect output with x11alpha

bugzilla-daemon at ghostscript.com bugzilla-daemon at ghostscript.com
Fri May 25 06:50:11 UTC 2012


http://bugs.ghostscript.com/show_bug.cgi?id=692663

--- Comment #17 from Hin-Tak Leung <hintak at ghostscript.com> 2012-05-25 06:50:09 UTC ---
Hmm, while it is nice and good work to find out the problem is due to the
combinations of different caching parameters not working properly, I think
there are two points to consider:

- the whole point of having a x11alpha in addition to x11 is that they are
different: trying to tune x11alpha to be more like x11 obviously avoid and work
around the issue concerned and 'works', but somewhat besides the point and
irrelevant.

- the fact that there are 3 numbers which are independently set-able and
explicitly set-able mean that they were intended to be independently and
explicitly set, I think.

So I think attempts to switch to, or find a magical combination that 'works',
without knowing why other combinations do not, sounds like voodoo... and also
setting numbers to max_int and allowing resources to run out-of-bound may have
bad consequences of another kind with other input files - e.g. rendering
problem is arguably not as serious a problem as resource exhaustion &
sluggishness & other processes getting randonly killed...

-- 
Configure bugmail: http://bugs.ghostscript.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.


More information about the gs-bugs mailing list