After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 720901 - Crash in g_hash_table_resize()
Crash in g_hash_table_resize()
Status: RESOLVED INCOMPLETE
Product: rhythmbox
Classification: Other
Component: general
3.0.x
Other Linux
: Normal critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-12-21 19:46 UTC by Milan Bouchet-Valat
Modified: 2015-06-13 11:14 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Milan Bouchet-Valat 2013-12-21 19:46:23 UTC 
Reported by two users (including me) in Fedora 20. I have no idea what caused this.

Rhythmbox 3.0-3

https://bugzilla.redhat.com/show_bug.cgi?id=1039771

+ Trace 232950

Thread 4 (Thread 0x7f3a63fff700 (LWP 4788))

  • #0 __GI___lxstat
    at ../sysdeps/unix/sysv/linux/wordsize-64/lxstat.c line 35
  • #1 lstat
    at /usr/include/sys/stat.h line 462
  • #2 _g_local_file_info_get
    at glocalfileinfo.c line 1699
  • #3 g_local_file_query_info
    at glocalfile.c line 1232
  • #4 stat_thread_main
    at rhythmdb.c line 839
  • #5 g_thread_proxy
    at gthread.c line 798
  • #6 start_thread
    at pthread_create.c line 309
  • #7 clone
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 111 






Comment 1


Milan Bouchet-Valat





          2013-12-21 19:47:57 UTC
        



Also seen with rhythmbox 3.0.1-1.






Comment 2


Jonathan Matthew





          2013-12-21 21:48:02 UTC
        



(In reply to comment #0)
> Reported by two users (including me) in Fedora 20. I have no idea what caused
> this.

Looks like heap corruption. Can you try reproducing it in valgrind?






Comment 3


Milan Bouchet-Valat





          2013-12-21 21:52:56 UTC
        



Sorry, I have no idea how to reproduce it. If I see it again I will run RB in Valgrind, but let's hope it's not too rare...

(I've also realized I've copied the wrong part of the backtrace... ;-)






Comment 4


Alexandre Franke





          2015-06-13 11:14:16 UTC
        



Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment.
Thanks!