Arch Linux

dimsuz

Member

Registered: 2011-05-01

Posts: 29

Rhythmbox 2.90.1 crashes on start

After upgrade to GNOME3 I got new rhythmbox that crashes more often

Today for example it started to crash on start.
I tried to valgrind it, here's the output just before the crash:

(rhythmbox:6892): Gtk-CRITICAL **: gtk_label_set_markup: assertion `GTK_IS_LABEL (label)' failed

(rhythmbox:6892): gnome-media-profiles-CRITICAL **: gm_audio_profile_choose_set_active_profile: assertion `GM_AUDIO_IS_PROFILE_CHOOSE (choose)' failed
==6892== Thread 1:
==6892== Invalid read of size 1
==6892==    at 0x48E8A7A: g_str_hash (in /usr/lib/libglib-2.0.so.0.2800.6)
==6892==    by 0x48B5D77: g_hash_table_lookup (in /usr/lib/libglib-2.0.so.0.2800.6)
==6892==    by 0x40E6A83: rb_refstring_new (rb-refstring.c:88)
==6892==    by 0x40E71E0: rhythmdb_entry_sync_mirrored (rhythmdb.c:3669)
==6892==    by 0x40EBFB0: rhythmdb_entry_get_string (rhythmdb.c:4757)
==6892==    by 0x40CEB1D: rb_entry_view_string_cell_data_func (rb-entry-view.c:1051)
==6892==    by 0x41FBDB4: ??? (in /usr/lib/libgtk-3.so.0.0.9)
==6892==    by 0x48B6312: g_hash_table_foreach (in /usr/lib/libglib-2.0.so.0.2800.6)
==6892==    by 0x41FBBD4: ??? (in /usr/lib/libgtk-3.so.0.0.9)
==6892==    by 0x4201868: ??? (in /usr/lib/libgtk-3.so.0.0.9)
==6892==    by 0x42C46E7: ??? (in /usr/lib/libgtk-3.so.0.0.9)
==6892==    by 0x483C77C: ??? (in /usr/lib/libgobject-2.0.so.0.2800.6)
==6892==  Address 0x0 is not stack'd, malloc'd or (recently) free'd
==6892== 
==6892== 
==6892== Process terminating with default action of signal 11 (SIGSEGV)
==6892==  Access not within mapped region at address 0x0
==6892==    at 0x48E8A7A: g_str_hash (in /usr/lib/libglib-2.0.so.0.2800.6)
==6892==    by 0x48B5D77: g_hash_table_lookup (in /usr/lib/libglib-2.0.so.0.2800.6)
==6892==    by 0x40E6A83: rb_refstring_new (rb-refstring.c:88)
==6892==    by 0x40E71E0: rhythmdb_entry_sync_mirrored (rhythmdb.c:3669)
==6892==    by 0x40EBFB0: rhythmdb_entry_get_string (rhythmdb.c:4757)
==6892==    by 0x40CEB1D: rb_entry_view_string_cell_data_func (rb-entry-view.c:1051)
==6892==    by 0x41FBDB4: ??? (in /usr/lib/libgtk-3.so.0.0.9)
==6892==    by 0x48B6312: g_hash_table_foreach (in /usr/lib/libglib-2.0.so.0.2800.6)
==6892==    by 0x41FBBD4: ??? (in /usr/lib/libgtk-3.so.0.0.9)
==6892==    by 0x4201868: ??? (in /usr/lib/libgtk-3.so.0.0.9)
==6892==    by 0x42C46E7: ??? (in /usr/lib/libgtk-3.so.0.0.9)
==6892==    by 0x483C77C: ??? (in /usr/lib/libgobject-2.0.so.0.2800.6)
==6892==  If you believe this happened as a result of a stack
==6892==  overflow in your program's main thread (unlikely but
==6892==  possible), you can try to increase the size of the
==6892==  main thread stack using the --main-stacksize= flag.
==6892==  The main thread stack size used in this run was 8388608.
==6892== 
==6892== HEAP SUMMARY:
==6892==     in use at exit: 29,986,115 bytes in 271,377 blocks
==6892==   total heap usage: 1,728,881 allocs, 1,457,504 frees, 264,797,045 bytes allocated
==6892== 
==6892== LEAK SUMMARY:
==6892==    definitely lost: 8,372 bytes in 60 blocks
==6892==    indirectly lost: 34,396 bytes in 1,682 blocks
==6892==      possibly lost: 12,242,740 bytes in 138,900 blocks
==6892==    still reachable: 17,700,607 bytes in 130,735 blocks
==6892==         suppressed: 0 bytes in 0 blocks
==6892== Rerun with --leak-check=full to see details of leaked memory
==6892== 
==6892== For counts of detected and suppressed errors, rerun with: -v
==6892== ERROR SUMMARY: 68019 errors from 87 contexts (suppressed: 0 from 0)
Killed

Any hints?