assertion failed in hash_timed_queue_removed while importing photos from F-Spot

Bug #898028 reported by Alex Peters
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Shotwell
Fix Released
Undecided
Unassigned
shotwell (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

$ shotwell
**
ERROR:x86_64-linux-gnu/TimedQueue.c:1150:hash_timed_queue_removed: assertion failed: (_tmp0_)
Aborted

While attempting to import an F-Spot collection (around 158,000 photos) into an existing Shotwell collection (around 48,500 photos), Shotwell terminated with the error message shown above after processing 16,968 F-Spot photos. These photos have remained within Shotwell and are visible in the Last Import list.

The import process ran for around 9 hours before failing, with "import preparation" occupying the first several of these hours; this suggests a polynomial (O(n^c)) or greater import processing time which might be another bug in itself.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: shotwell 0.9.3-0ubuntu0.1
ProcVersionSignature: Ubuntu 2.6.38-12.51-generic 2.6.38.8
Uname: Linux 2.6.38-12-generic x86_64
Architecture: amd64
Date: Wed Nov 30 17:00:38 2011
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: shotwell
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Alex Peters (alex-peters) wrote :
Revision history for this message
Clint Rogers (clinton-yorba) wrote :

Hi, and thank you for reporting this.

Here are some things you might try that could help:

1. Upgrade your Shotwell package to the latest one available in the repository for Natty Narwhal (which should be 0.10).
2. Try rerunning the scenario with debugging enabled and with a smaller import; if this triggers the crash a second time, it'll provide logging info, and hopefully some insight into what happened immediately before the assertion.

In the meantime, I'll talk to my team lead about possibly relaxing this assertion; what seems to be happening is that, in removed(), it's complaining that an item isn't in the hash map before it sets out to remove it. It may be possible to safely fail silently in that case (to wit: whatever I was supposed to remove is already gone or never got added to begin with, so my work here is done).

As for import speed, and indeed, speed in general with larger libraries, it's very much on our minds; please have a look at http://redmine.yorba.org/issues/3980 (the numbers you posted above will be added to the bug).

Revision history for this message
Clint Rogers (clinton-yorba) wrote :

The offending assertion has been ticketed at http://redmine.yorba.org/issues/4461.

Revision history for this message
Alex Peters (alex-peters) wrote :

Thanks for your prompt and significant action on this ticket.

Could you please let me know how to enable debugging? Shotwell doesn't accept a --debug command line option, and a Google search for "shotwell debug" doesn't return any obvious answers.

I don't have direct access to the computer affected (it belongs to extended family), but when I next do--and am equipped to generate debug output--I will provide further information ASAP.

Revision history for this message
Adam Dingle (adam-yorba) wrote :

Alex,

there are a couple of things you can helpfully do:

1. Enable logging. To do this, run "SHOTWELL_LOG=1 shotwell" from a command prompt. As Shotwell runs, it will write a log file to ~/.cache/shotwell/shotwell.log.

2. Run Shotwell under GDB. That way when Shotwell crashes you'll get a stack trace, which could be helpful. See

http://redmine.yorba.org/projects/shotwell/wiki/ShotwellFAQ#I-found-a-bug-in-Shotwell-How-can-I-report-it

Changed in shotwell (Ubuntu):
status: New → Fix Committed
importance: Undecided → Low
Changed in shotwell:
status: New → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package shotwell - 0.11.91-0ubuntu1

---------------
shotwell (0.11.91-0ubuntu1) precise; urgency=low

  * New upstream version using GTK3 (lp: #871034),
    should fix lp: #800459, #881896, #887357, #888363, #898028
  * Refreshed patches for the new version
  * debian/control:
    - updated build-dependencies for GTK3
  * debian/patches/99git_libraw_api.patch:
    - dropped, the patch is in the new version
 -- Sebastien Bacher <email address hidden> Wed, 11 Jan 2012 15:59:04 +0100

Changed in shotwell (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.