Shotwell crashes when regenerating large numbers of thumbnails
Submitted by Lucas Beeler
Link to original bug (#718982)
Description
---- Reported by lucas@yorba.org 2013-03-13 16:56:00 -0700 ----
Original Redmine bug id: 6543
Original URL: http://redmine.yorba.org/issues/6543
Searchable id: yorba-bug-6543
Original author: Lucas Beeler
Original description:
Steps to reproduce:
#Set up Shotwell such that it manages a library of at least 500 photos
#Quit Shotwell
#Delete the ~/.cache/shotwell directory and its contents
#Start Shotwell
#Ensure the "Library" page is being viewed
#With the mouse wheel, rapidly scroll downward through the library
You should see a crash with an assertion error like the following:
ERROR:/build/buildd/shotwell-0.14.0pr1+2348~quantal1/src/core/DataSource.vala:424:data_source_contact_subscribers: assertion failed: (!in_contact)
Aborted (core dumped)
Related issues:
- related to shotwell - 7447: Shotwell crashes when import large numbers of photos (Need Information)
---- Additional Comments From shotwell-maint@gnome.bugs 2013-05-16 14:44:00 -0700 ----
History
Comment 1
Updated by Lucas Beeler 8 months ago
- Priority changed from Urgent to High
Downgrading from urgent to high. This is reproducible, but barely. It is also highly dependent on how long it takes to thumbnail the objects in the view. For example, RAW files and huge JPEGs seem to cause this crash much more readily than small JPEGs.
Comment 2
Updated by Jim Nelson 8 months ago
- Target version changed from 0.14.0 to 0.15.0
Comment 3
Updated by Jim Nelson 8 months ago
- Target version changed from 0.15.0 to 0.16.0
Comment 4
Updated by Jim Nelson 6 months ago
-
Target version deleted (
<strike>
_0.16.0_</strike>
)
--- Bug imported by chaz@yorba.org 2013-11-25 21:59 UTC ---
This bug was previously known as bug 6543 at http://redmine.yorba.org/show_bug.cgi?id=6543
Unknown version " in product shotwell. Setting version to "!unspecified". Unknown milestone "unknown in product shotwell. Setting to default milestone for this product, "---". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one. Resolution set on an open status. Dropping resolution
Resolution: RESOLVED OBSOLETE