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.
Created attachment 149472 [details] example corrupt jpeg
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]