Bug 4780 - YAM: Cannot read some JPEG files (1GI6ZEN)
Summary: YAM: Cannot read some JPEG files (1GI6ZEN)
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 2.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 2.0 M1   Edit
Assignee: Carolyn MacLeod CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-10-11 14:22 EDT by Mike Wilson CLA
Modified: 2002-03-07 10:23 EST (History)
0 users

See Also:

Attachments
Here is the broken JPEG: serverinstance.jpg (87.92 KB, image/jpeg)
2001-12-11 10:06 EST, Carolyn MacLeod CLA 		no flags Details
View All 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 Mike Wilson CLA 2001-10-11 14:22:53 EDT 
prefix        p
name          181900
reference     
abstract      OTI: cannot read some JPEG file
duplicate     

state         open                        priority                          
severity      3                           target                            
age           0                           due                               
product                         hasApar                           

compName      wsa.web.oti                 answer                            
release                                   symptom       io                  
envName                                   phaseFound    dt                  
level                                     phaseInject                       

addDate       2001/08/09 04:25:14         assignDate    2001/08/09 04:25:14 
lastUpdate    2001/08/09 04:47:18         responseDate                      
endDate                                

ownerLogin    decandio                    originLogin   jins                
ownerName     George DeCandio             originName    Satoh, Hitoshi      
ownerArea     9ZVA                        originArea    SA710               

apar                                      pmr                          
test                                                                                               

tracks: none.

verify: none.

history:
    addDate              action          userLogin (userName)
    -------------------- --------------- ----------------------------------
    2001/08/09 04:25:18  open            jins (Satoh, Hitoshi)
    2001/08/09 04:47:19  note            jins (Satoh, Hitoshi)

duplicate defects: none.

duplicate features: none.

sizing: none.

notes:
    <Note by jins (Satoh, Hitoshi), 2001/08/09 04:25:15, seq: 1 rel: 0  action: open>
SWT JPEG reader cannot read the file
"serverinstance.jpg" which is located at
 IBM Web Tooling Resources
  plugins
   com.ibm.etools.webtools
    Examples
     YourCo
      WebApplication
       images

    <Note by jins (Satoh, Hitoshi), 2001/08/09 04:47:18, seq: 2 rel: 0  action: note>
SWT JPEG Reader expects JPEG data stream to start with following 4 bytes.

offset data
0      0xFF 1st byte of SOI marker
1      0xD8 2nd byte of SOI marker
2      0xFF 1st byte of APPn marker
3      0xEn 2nd byte of APPn marker (varies from 0xE0 to 0xEF)

the file contains 0xFE (2nd byte of JPG14 marker) instead of 0xEn as 4th byte.
JPEG reader should read this file,
as alomost all image viewers and image readers read this file.

It should be modified not to check 4th byte.
It seems that the modification causes no side effects.




NOTES:
Comment 1 DJ Houghton CLA 2001-10-29 16:38:03 EST 
PRODUCT VERSION:
	R09, Win 2000
Comment 2 Carolyn MacLeod CLA 2001-12-10 16:48:52 EST 
The problem has been fixed according to the description (we no longer check for 
APPN at all, i.e. the only requirement for isJPEGFile to return true is if SOI 
(FFD8) is in the first 2 bytes).

But this has not been tested ith the original problem image. Sent email to GdC 
asking for the original image to be attached to this bug report.
Comment 3 Carolyn MacLeod CLA 2001-12-11 10:06:12 EST 
Created attachment 164 [details]
Here is the broken JPEG: serverinstance.jpg
Comment 4 Carolyn MacLeod CLA 2001-12-11 10:07:10 EST 
Tested the broken JPEG, and we are able to read it now.