Bug 691628 - Time consuming and incorrect rendering
Summary: Time consuming and incorrect rendering
Status: RESOLVED FIXED
Alias: None
Product: Ghostscript
Classification: Unclassified
Component: PS Interpreter (show other bugs)
Version: 9.00
Hardware: Other Linux
: P4 normal
Assignee: Alex Cherepanov
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-19 10:46 UTC by av1474
Modified: 2011-04-09 05:26 UTC (History)
3 users (show)

See Also:
Customer:
Word Size: ---


Attachments
sample file (4.07 MB, application/pdf)
2010-09-19 14:41 UTC, Alex Cherepanov
Details

Note You need to log in before you can comment on or make changes to this bug.
Description av1474 2010-09-19 10:46:36 UTC
First page of http://www.monotypefonts.com/PDFs/OTPGill.pdf takes
more than 10 seconds to render on this (low spec) machine the result
is incorrect (compared to xpdf) too.

FWIW ghostscript 8.71 and 9.0 segfault on this document.
Comment 1 Alex Cherepanov 2010-09-19 14:41:38 UTC
Created attachment 6737 [details]
sample file

This is a local copy of the sample file.

The color space of the image on the first page is rather complicated.
It's Indexed color space with DeviceN base color space and Lab alternative
color space. I'm not sure whether every attribute is set up correctly there.

My copy of gswin32c doesn't crash but the image has wild green colors.
Comment 2 Alex Cherepanov 2010-09-20 02:54:40 UTC
SEGV is reproduced on 64-bit Linux with x11alpha device.
x11 renders the image with the same green colors as Windows.

The color bug is a recent regression. V. 8.71 shows the file
just fine on x11 or Windows display device.

The PDF file itself looks correct.
Comment 3 Tor Andersson 2010-10-20 21:32:42 UTC
I've fixed the performance issue in MuPDF. Alex, do you want to keep the bug open for the ghostscript issues?
Comment 4 av1474 2010-10-20 22:59:58 UTC
Performance was improved no question about it, but the correctness wasn't, first
page is still misrendered with mupdf.
Comment 5 av1474 2010-10-21 04:34:49 UTC
And I take that back, the page is rendered correctly (was using wrong library,
sorry about that)
Comment 6 Michael Vrhel 2011-04-09 05:26:25 UTC
fixed with rev 12380