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

[Launchpad Bug Tracker]

This bug was fixed in the package f-spot - 0.7.2-1

---------------
f-spot (0.7.2-1) experimental; urgency=low

  * New upstream release 0.7.2 "Retooled"
    + Third release of the unstable 0.7 development series. Features a
      fully restructured source tree with full Monodevelop build
      support. Solves some of the regressions introduced in 0.7.1.
    + Reorganized source tree for clarity, builds with Monodevelop.
    + Switched from QueuedSqliteDatabase to HyenaSqliteConnection (Mike
      Gemünde)
    + Build tweaks (Christian Krause)
    + More GtkBuilder transition (Eric Faehnrich) 
    + Reliability improvements (lots of them) for metadata handling (Mike
      Gemünde, Ruben Vermeersch)
    + Prune empty directories when deleting photos, import usability
      enhancements (Mike Wallick)
    + Big race-condition fix in import (Paul Wellner Bou)
    + Loads of improvements to Taglib#, in terms of handling broken files,
      extra format support (Pentax, Panasonic, Leica), stability and
      correctness (Ruben Vermeersch)
      - Runs out of memory Importing photo with suspect EXIF data
        (LP: #272822)
      - Metadata parsing of broken file causes large memory allocation
        (LP: #597720)
      - Photo import: cancel & copy have same keyboard shortcut (LP: #244423)
      - Facebook export will not create new album (LP: #563495)
      - Allow export to iPod (LP: #518344)
    + Reporting of import errors.
    + Speedups to repeated imports of the same directory.
    + Piles of cleanups and general stability improvements.
    + Over 50 bugs closed (http://bit.ly/cqpC3y)
 -- Iain Lane <iain at orangesquash.org.uk>   Tue,  17 Aug 2010 12:59:32 +0100

** Changed in: f-spot (Ubuntu)
       Status: Fix Committed => Fix Released

-- 
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 Personal photo management for the GNOME desktop: Fix Released
Status in “f-spot” package in Ubuntu: Fix Released

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