Occasionally, a crash occurs if tags are moved around with metadata writing enabled while an import of images containing metadata is happening.
Submitted by cli..@..ba.org
Link to original bug (#717911)
Description
---- Reported by clinton@yorba.org 2011-09-19 14:05:00 -0700 ----
Original Redmine bug id: 4144
Original URL: http://redmine.yorba.org/issues/4144
Searchable id: yorba-bug-4144
Original author: Clinton Rogers
Original description:
Steps to reproduce:
With a library containing multiple tags, start a large import of images that already contain tags in their metadata.
During the import, repeatedly drag tags underneath each other.
Notice that the following error appears in the console:
ERROR:meh/sidebar/Branch.c:845:sidebar_branch_node_remove_child: assertion failed: (self->children != NULL)
...at which point Shotwell aborts.
A backtrace has been captured and is included.
Related issues:
- related to shotwell - 7447: Shotwell crashes when import large numbers of photos (Need Information)
---- Additional Comments From shotwell-maint@gnome.bugs 2012-03-26 15:48:00 -0700 ----
History
Comment 1
Updated by Clinton Rogers about 2 years ago
- File 4144-backtrace.txt added
Comment 2
Updated by Clinton Rogers about 2 years ago
- Subject changed from Occasionally, a crash occurs if tags are moved with metadata writing enable while an import of images containing metadata is happening. to Occasionally, a crash occurs if tags are moved around with metadata writing enabled while an import of images containing metadata is happening.
Comment 3
Updated by Jim Nelson about 2 years ago
I reproduced a crash as well moving around tags and then undoing them while metadata writing was going on. (Note that no import was occurring, but a lot of metadata writing was happening.) However, this didn't cause an assertion failure but a database constraint error:
(TagTable.create_from_row) [19] - constraint failed
which causes a hard exit and thereby no stack trace.
Comment 4
Updated by Jim Nelson about 2 years ago
- File 4144.txt added
I reproduced this again by moving tags around with metadata writing turned on, undoing and redoing the actions while the writing occurred. This time it was this assertion:
ERROR:build/Commands.c:8060:reparent_tag_command_restore_child_attachments_at: assertion failed: (tmp22)
Stack trace attached.
Comment 5
Updated by Lucas Beeler about 2 years ago
I can't speak to the database error, but at least as far as the assertion failure mentioned in posting #4 (closed), I believe this to be fixed in 4f826ff6.
Comment 6
Updated by Jim Nelson about 2 years ago
- Target version changed from 0.11.2 to 0.12
We won't be able to fix all cases of this bug. Let's attack this in 0.12.
Comment 7
Updated by Adam Dingle almost 2 years ago
- Priority changed from Urgent to High
Comment 8
Updated by Adam Dingle over 1 year ago
-
Target version deleted (
<strike>
_0.12_</strike>
)
--- Bug imported by chaz@yorba.org 2013-11-25 21:54 UTC ---
This bug was previously known as bug 4144 at http://redmine.yorba.org/show_bug.cgi?id=4144 Imported an attachment (id=262132) Imported an attachment (id=262133)
Unknown Component Using default product and component set in Parameters 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