Bug 231318 - corrupt jpegs freeze f-spot during import
corrupt jpegs freeze f-spot during import
Status: CLOSED CURRENTRELEASE
Product: Fedora
Classification: Fedora
Component: f-spot (Show other bugs)
6
All Linux
medium Severity high
: ---
: ---
Assigned To: Christopher Aillon
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-03-07 13:15 EST by Jason Farrell
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version: f-spot-0.3.5-2.fc7
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-06-23 02:44:03 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
example corrupt jpeg (30.60 KB, image/jpeg)
2007-03-07 13:16 EST, Jason Farrell
no flags Details

  None (edit)
Description Jason Farrell 2007-03-07 13:15:15 EST
Description of problem:
Certain corrupt jpeg's can freeze f-spot during the lengthy import process. The
only way to proceed is to run f-spot from the terminal to figure out on what
files it hangs, remove them, manually kill f-spot, then repeat. Not good.

Version-Release number of selected component (if applicable):
f-spot-0.2.1-1.fc6

How reproducible:
always

Steps to Reproduce:
1. attempt to import a folder containing a corrupt jpeg. not just any garbage
data will do - see attachment below.
  
Actual results:
f-spot frozen.

Expected results:
all garbage data ignored, and import successful.
Comment 1 Jason Farrell 2007-03-07 13:16:31 EST
Created attachment 149472 [details]
example corrupt jpeg
Comment 2 Jason Farrell 2007-06-23 02:44:03 EDT
appears to be fixed now. throws an exception instead of freezing.

Exeption while reading jpeg headers
System.Exception: Invalid marker found 52
  at JpegHeader+Marker.Load (System.IO.Stream stream) [0x00000]
  at JpegHeader.Load (System.IO.Stream stream, Boolean metadata_only) [0x00000]
  at JpegHeader..ctor (System.IO.Stream stream, Boolean metadata_only) [0x00000]

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