[ubuntu-mono] [Bug 597720] [NEW] Max CPU and memory grows on photo import

[Chris Hatch]

Public bug reported:

Binary package hint: f-spot

See attached jpg file. When I import this the CPU maxes out and memory
grows and grows until i kill the process.

I see the following in standard out after the import is kicked off:

item ImportCommand+SourceItem
cleanup context
cleanup context
FSpot.Tiff.ShortReadException: Short Read
  at FSpot.Tiff.DirectoryEntry.LoadExternal (System.IO.Stream stream) [0x00000] 
  at FSpot.Tiff.ImageDirectory.LoadEntries (System.IO.Stream stream) [0x00000] 
  at FSpot.Tiff.ImageDirectory.Load (System.IO.Stream stream) [0x00000] 
  at FSpot.Tiff.ImageDirectory..ctor (System.IO.Stream stream, UInt32 start_position, Endian endian) [0x00000] 
  at FSpot.Tiff.Header..ctor (System.IO.Stream stream) [0x00000] 
  at JpegHeader.GetExifHeader () [0x00000] 
  at FSpot.JpegFile.get_ExifHeader () [0x00000] 
  at FSpot.JpegFile.get_Date () [0x00000] 

The image file raises a dialog when opened in GIMP also. See attached.
Something about embedded color profile. If I say yes to this dialog,
save the file and then try the import again it works fine. So something
in the file is causing this max out in f-spot.

ProblemType: Bug
Architecture: amd64
Date: Wed Jun 23 23:09:26 2010
DistroRelease: Ubuntu 9.10
Package: f-spot 0.6.1.5-0ubuntu1
ProcEnviron:
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-22.60-generic
SourcePackage: f-spot
Uname: Linux 2.6.31-22-generic x86_64

** Affects: f-spot (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug

-- 
Max CPU and memory grows on photo import
https://bugs.launchpad.net/bugs/597720
You received this bug notification because you are a member of Ubuntu
CLI/Mono Uploaders, which is subscribed to f-spot in ubuntu.

Status in “f-spot” package in Ubuntu: New

Bug description:
Binary package hint: f-spot

See attached jpg file. When I import this the CPU maxes out and memory grows and grows until i kill the process.

I see the following in standard out after the import is kicked off:

item ImportCommand+SourceItem
cleanup context
cleanup context
FSpot.Tiff.ShortReadException: Short Read
  at FSpot.Tiff.DirectoryEntry.LoadExternal (System.IO.Stream stream) [0x00000] 
  at FSpot.Tiff.ImageDirectory.LoadEntries (System.IO.Stream stream) [0x00000] 
  at FSpot.Tiff.ImageDirectory.Load (System.IO.Stream stream) [0x00000] 
  at FSpot.Tiff.ImageDirectory..ctor (System.IO.Stream stream, UInt32 start_position, Endian endian) [0x00000] 
  at FSpot.Tiff.Header..ctor (System.IO.Stream stream) [0x00000] 
  at JpegHeader.GetExifHeader () [0x00000] 
  at FSpot.JpegFile.get_ExifHeader () [0x00000] 
  at FSpot.JpegFile.get_Date () [0x00000] 

The image file raises a dialog when opened in GIMP also. See attached. Something about embedded color profile. If I say yes to this dialog, save the file and then try the import again it works fine. So something in the file is causing this max out in f-spot.

ProblemType: Bug
Architecture: amd64
Date: Wed Jun 23 23:09:26 2010
DistroRelease: Ubuntu 9.10
Package: f-spot 0.6.1.5-0ubuntu1
ProcEnviron:
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-22.60-generic
SourcePackage: f-spot
Uname: Linux 2.6.31-22-generic x86_64