GNOME Bugzilla – Bug 647032
When clicking on "MIssing files" I get crash
Last modified: 2011-12-28 17:52:17 UTC
When %subj% with rhythmbox-2.90.1-6.git20110328.fc15.x86_64 RB 100% crashes with this backtrace: Program received signal SIGSEGV, Segmentation fault. g_str_hash (v=0x0) at gstring.c:142 142 for (p = v; *p != '\0'; p++) Missing separate debuginfos, use: debuginfo-install adwaita-gtk3-theme-2.91.93-3.fc15.x86_64 libicu-4.4.2-8.fc16.x86_64 librsvg2-2.32.1-3.fc16.x86_64 (gdb) t a a b Thread 7 (Thread 0x7fffd9911700 (LWP 22190)): Breakpoint 1 at 0x3ad3862fe0: file gstring.c, line 142. Thread 5 (Thread 0x7fffe82ce700 (LWP 22174)): Note: breakpoint 1 also set at pc 0x3ad3862fe0. Breakpoint 2 at 0x3ad3862fe0: file gstring.c, line 142. Thread 2 (Thread 0x7ffff0dd3700 (LWP 22156)): Note: breakpoints 1 and 2 also set at pc 0x3ad3862fe0. Breakpoint 3 at 0x3ad3862fe0: file gstring.c, line 142. Thread 1 (Thread 0x7ffff7fa49e0 (LWP 22121)): Note: breakpoints 1, 2 and 3 also set at pc 0x3ad3862fe0. Breakpoint 4 at 0x3ad3862fe0: file gstring.c, line 142. (gdb) thread apply all backtrace (gdb) thread apply all backtrace
+ Trace 226629
Thread 1 (Thread 0x7ffff7fa49e0 (LWP 22121))
(gdb) q A debugging session is active. Inferior 1 [process 22121] will be killed. Quit anyway? (y or n) y
Created attachment 185428 [details] output of valgrind --leak-check=full --track-origins=yes -v rhythmbox
NULL value, might be caused by the %e code used. (rhythmbox:6194): Rhythmbox-WARNING **: eel_strdup_strftime does not support non-standard escape code %e ==6194== Invalid read of size 1 ==6194== at 0x3AD3862FE0: g_str_hash (gstring.c:142) ==6194== by 0x3AD383206C: g_hash_table_lookup (ghash.c:313) ==6194== by 0x35014A4014: rb_refstring_new (rb-refstring.c:88) ==6194== by 0x35014A47A6: rhythmdb_entry_sync_mirrored (rhythmdb.c:3681) ==6194== by 0x35014A9215: rhythmdb_entry_get_string (rhythmdb.c:4790) ==6194== by 0x350148E3FB: rb_entry_view_string_cell_data_func (rb-entry-view.c:1115) ==6194== by 0x34FE899454: apply_cell_attributes (gtkcellarea.c:1281) ==6194== by 0x3AD3832572: g_hash_table_foreach (ghash.c:1330) ==6194== by 0x34FE899305: gtk_cell_area_real_apply_attributes (gtkcellarea.c:1310) ==6194== by 0x34FE89ED18: gtk_cell_area_box_apply_attributes (gtkcellareabox.c:1320) ==6194== by 0x3AD800E2ED: g_closure_invoke (gclosure.c:767) ==6194== by 0x3AD801E941: signal_emit_unlocked_R (gsignal.c:3182) ==6194== Address 0x0 is not stack'd, malloc'd or (recently) free'd This will crash for af, cs and hu translations. Either we need to add "%e" to be supported, or fix the translation comments to mention what's supported.
Looks like it's not the crasher, will file a separate bug.
Created attachment 185431 [details] LANG=en_US valgrind --track-origins=yes -v rhythmbox Now it crashed even without clicking anything just on its own.
Filed as bug 647050
*** Bug 648649 has been marked as a duplicate of this bug. ***
*** Bug 648711 has been marked as a duplicate of this bug. ***
New version of rhythmbox (rhythmbox-2.90.1-9.git20110502.fc15.x86_64) and this crash on startup: Program received signal SIGSEGV, Segmentation fault. g_str_hash (v=0x0) at gstring.c:142 142 for (p = v; *p != '\0'; p++) Missing separate debuginfos, use: debuginfo-install libicu-4.4.2-8.fc16.x86_64 librsvg2-2.32.1-3.fc16.x86_64 (gdb) thread apply all backtrace
+ Trace 226987
Thread 1 (Thread 0x7ffff79349e0 (LWP 3787))
*** Bug 650358 has been marked as a duplicate of this bug. ***
Copying and pasting https://bugzilla.gnome.org/show_bug.cgi?id=650358#c2 here : Looking at rhythmdb_entry_sync_mirrored, rb_refsting_new is called with the result of val = rb_utf_friendly_time (entry->last_seen); which returns NULL when entry->last_seen is 0, which is the case here, so this would explain the bug. Looking at the backtrace from bug #647032 this indeed looks like a duplicate, I was confused by the initial comments from hadess, didn't pay attention he said it was a different bug.
fixed in commit c8e1896
Downstream bug with plenty of duplicates is https://bugzilla.redhat.com/show_bug.cgi?id=699290
*** Bug 655525 has been marked as a duplicate of this bug. ***