Bug 87517 - Repeatable libjpeg crash
Repeatable libjpeg crash
Product: Red Hat Linux
Classification: Retired
Component: libjpeg (Show other bugs)
i686 Linux
medium Severity low
: ---
: ---
Assigned To: Matthias Clasen
Depends On:
  Show dependency treegraph
Reported: 2003-03-27 22:33 EST by jonny robertson
Modified: 2007-04-18 12:52 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-05-12 17:36:31 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description jonny robertson 2003-03-27 22:33:05 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2) Gecko/20021202

Description of problem:
Specific jpg I have can repeatably crash applications that use libjpeg to render
the image (gqview, nautilis etc.).

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. run gqview or nautilis
2. browse to directory where 'bad' jpeg is located (dload from supplied URL)

Actual Results:  Program received signal SIGSEGV, Segmentation fault.
0x405bd5a0 in ycck_cmyk_convert (cinfo=0xc6, input_buf=0x8147870, input_row=1,
output_buf=0xbfffdce4, num_rows=0) at jdcolor.c:278
278           outptr[0] = range_limit[MAXJSAMPLE - (y + Crrtab[cr])];   /* red */

Expected Results:  Should just complain about a corrupt jpeg.

Additional info:

libjpeg seems to handle this image okay on RH 7.3.
Comment 1 Matthias Clasen 2004-05-12 17:36:31 EDT
The URL is dangling. Can't reproduce or fix this without the offending
Comment 2 Mark Henson 2004-05-12 17:43:59 EDT
The URL has been fixed.
Comment 3 jonny robertson 2004-05-12 18:04:39 EDT
I can't reproduce this in FC1 anyway (libjpeg-6b-29).... guess it was
fixed upstream at some point.  Feel free to leave it closed if you want.

Note You need to log in before you can comment on or make changes to this bug.