GNOME Bugzilla – Bug 650358
When just running OGG file from my disc while the dabase is being refreshed, RB crashes
Last modified: 2011-05-17 02:18:59 UTC
With RB rhythmbox-2.90.1-9.git20110502.fc15.x86_64 And yes, when doing in thread 1, frame 4 print entry->last_seen I got 0 as the result. --------------------------------- 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 dbus-python-0.83.0-8.fc15.x86_64 flac-1.2.1-6.fc12.x86_64 gamin-0.1.10-9.fc15.x86_64 gstreamer-plugins-bad-free-0.10.22-1.fc15.x86_64 gstreamer-plugins-good-0.10.29-1.fc15.x86_64 libXtst-1.2.0-2.fc15.x86_64 libasyncns-0.8-2.fc15.x86_64 libicu-4.4.2-8.fc16.x86_64 librsvg2-2.32.1-3.fc16.x86_64 libsndfile-1.0.24-1.fc15.x86_64 pycairo-1.8.8-2.fc14.x86_64 tcp_wrappers-libs-7.6-60.fc15.x86_64 (gdb) thread apply all backtrace (gdb) thread apply all backtrace
+ Trace 227152
Thread 1 (Thread 0x7ffff6dd49e0 (LWP 7657))
(gdb)
b.g.o suggested that this is a duplicate of my other bug 647032.
The interesting bit of the backtrace is
+ Trace 227153
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.
*** This bug has been marked as a duplicate of bug 647032 ***