Sidebar assertion [norepro]
Submitted by Eric Gregory
Assigned to Eric Gregory
Link to original bug (#717947)
Description
---- Reported by eric@yorba.org 2011-09-06 19:03:00 -0700 ----
Original Redmine bug id: 4104
Original URL: http://redmine.yorba.org/issues/4104
Searchable id: yorba-bug-4104
Original author: Eric Gregory
Original description:
While trying to view Offline photos, I got this nasty surprise from the sidebar:
bq.
@l 26682 2011-09-06 18:54:54 [CRT] sidebar_tree_get_wrapper_at_path: assertion `path != NULL' failed
Program received signal SIGSEGV, Segmentation fault.
0x081c1ddf in sidebar_tree_real_button_press_event (base=0x8840020,
event=0x891c8a8) at build/sidebar/Tree.c:2765
2765 tmp15 = SIDEBAR_IS_RENAMEABLE_ENTRY (tmp14->entry);
(gdb) bt
#0 0x081c1ddf in sidebar_tree_real_button_press_event (base=0x8840020,
event=0x891c8a8) at build/sidebar/Tree.c:2765
#1 0x01affa04 in _gtk_marshal_BOOLEAN__BOXED (closure=0x859ef60,
return_value=0xbfffebc4, n_param_values=2, param_values=0xb38a8aa0,
invocation_hint=0xbfffebb0, marshal_data=0x81c1a9b)
at /build/buildd/gtk+2.0-2.24.4/gtk/gtkmarshalers.c:86
#2 0x021d7cc7 in g_type_class_meta_marshal (closure=0x859ef60,
return_value=0xbfffebc4, n_param_values=2, param_values=0xb38a8aa0,
invocation_hint=0xbfffebb0, marshal_data=0xb0)
at /build/buildd/glib2.0-2.28.6/./gobject/gclosure.c:878
#3 0x021d9372 in g_closure_invoke (closure=0x859ef60,
return_value=0xbfffebc4, n_param_values=2, param_values=0xb38a8aa0,
invocation_hint=0xbfffebb0)
at /build/buildd/glib2.0-2.28.6/./gobject/gclosure.c:767
#4 0x021ebe45 in signal_emit_unlocked_R (node=0x85a0740, detail=0,
instance=0x8840020, emission_return=0xbfffecfc,
instance_and_params=0xb38a8aa0)
at /build/buildd/glib2.0-2.28.6/./gobject/gsignal.c:3290
#5 0x021f48d7 in g_signal_emit_valist (instance=0x8840020, signal_id=33,
detail=0,
var_args=0xbfffed70 "234355377277XM[b2303553772773643573310136435733101") at /build/buildd/glib2.0-2.28.6/./gobject/gsignal.c:2993
#6 0x021f4cc2 in g_signal_emit (instance=0x8840020, signal_id=33, detail=0)@
So far, no luck reproducing this issue.
Putting on 0.11.1 for discussion.
---- Additional Comments From shotwell-maint@gnome.bugs 2013-05-01 11:38:00 -0700 ----
History
Comment 1
Updated by Adam Dingle about 2 years ago
- Priority changed from Normal to High
Comment 2
Updated by Eric Gregory about 2 years ago
- Assignee set to Eric Gregory
- Priority changed from High to Normal
Still not sure what's causing this, but it happened again, and again it was just after an import.
It seems the problem is in button_press_event. When path is null, we shouldn't be calling get_wrapper_at_path(path)
Comment 3
Updated by Eric Gregory about 2 years ago
- Status changed from Open to Review
Comment 4
Updated by Adam Dingle about 2 years ago
- Priority changed from Normal to High
All tickets with target versions should have a Priority of at least High. :)
Comment 5
Updated by Eric Gregory about 2 years ago
- Status changed from Review to 5
- Resolution set to fixed
Fixed in 92b7c0d2
Comment 6
Updated by Charles Lindsay 7 months ago
- Status changed from 5 to Fixed
--- Bug imported by chaz@yorba.org 2013-11-25 21:54 UTC ---
This bug was previously known as bug 4104 at http://redmine.yorba.org/show_bug.cgi?id=4104
Unknown Component Using default product and component set in Parameters 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.
Version: 0.11.1
Resolution: RESOLVED FIXED