Bug 694554 - Images not rendered
Summary: Images not rendered
Status: RESOLVED INVALID
Alias: None
Product: MuPDF
Classification: Unclassified
Component: mupdf (show other bugs)
Version: 1.2
Hardware: PC Linux
: P4 normal
Assignee: Tor Andersson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-09-01 13:33 UTC by OLCC
Modified: 2013-09-02 01:27 UTC (History)
1 user (show)

See Also:
Customer:
Word Size: ---


Attachments
Page with images that are not rendered bu mupdf (318.73 KB, application/pdf)
2013-09-01 13:33 UTC, OLCC
Details

Note You need to log in before you can comment on or make changes to this bug.
Description OLCC 2013-09-01 13:33:26 UTC
Created attachment 10161 [details]
Page with images that are not rendered bu mupdf

Images are not rendered for this page. Xpdf renders them without problem.

The following error is output:
"""
error: jpeg error: JPEG parameter struct mismatch: library thinks size is 656, caller expects 624
warning: Ignoring error during interpretation
"""
Comment 1 OLCC 2013-09-01 13:46:42 UTC
Images are rendered OK with mupdf version 0.9-2 from Debian.
Comment 2 Robin Watts 2013-09-01 17:03:05 UTC
That error message is an indication that you are building with the headers from one jpeglib version, but linking with the lib from another version. Hence no JPEG image will decode.

Build it properly, and your problems will go away.
Comment 3 Hin-Tak Leung 2013-09-02 01:27:54 UTC
(In reply to comment #2)
> That error message is an indication that you are building with the headers
> from one jpeglib version, but linking with the lib from another version.
> Hence no JPEG image will decode.
> 
> Build it properly, and your problems will go away.

Slightly mis-worded, given 'version' has a specific meaning... it can happen to the same library version compiled differently (different optimization/padding). I'd rather have phased it differently: the built-time jpeg library is different from the run-time jpeg library - if you build mupdf against the same library binaries on the same machine/system as where you intend to run mupdf, the problem will go away. i.e. do not build on one machine and run on another.