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 346664 - crash in rhythmbox when clicking in different items on the albums treeview
crash in rhythmbox when clicking in different items on the albums treeview
Status: RESOLVED DUPLICATE of bug 349601
Product: rhythmbox
Classification: Other
Component: User Interface
HEAD
Other Linux
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-07-05 15:46 UTC by Diego González
Modified: 2006-08-12 01:13 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Diego González 2006-07-05 15:46:00 UTC
If i click several times on the Albums treeview (the one that only has album titles) going up and down, for example:

Albums
Album 1
Album 2
Album 3
Album 4
Album 5
Album 6

If i click on Album 3, then Album 2, then Album 6, rhythmbox crashes.

I'm using rhythmbox HEAD, don't know if the problem is in the aplication itself.

On the console i get:

(rhythmbox:29121): GLib-GObject-WARNING **: invalid unclassed pointer in cast to `GObject'

(rhythmbox:29121): GLib-GObject-WARNING **: invalid unclassed pointer in cast to `GObject'


The backtrace is:

  • #0 IA__g_object_unref
    at gobject.c line 1734
  • #1 rhythmdb_event_free
    at rhythmdb.c line 522
  • #2 rhythmdb_process_events
    at rhythmdb.c line 1759
  • #3 rhythmdb_idle_poll_events
    at rhythmdb.c line 1788
  • #4 g_timeout_dispatch
    at gmain.c line 3420
  • #5 g_main_dispatch
    at gmain.c line 2043
  • #6 IA__g_main_context_dispatch
    at gmain.c line 2594
  • #7 g_main_context_iterate
    at gmain.c line 2675
  • #8 IA__g_main_loop_run
    at gmain.c line 2879
  • #9 IA__gtk_main
    at gtkmain.c line 1000
  • #10 main
    at main.c line 375

Comment 1 Kristian Rietveld 2006-07-05 15:48:03 UTC
The trace doesnt look like it has anything to do with GtkTreeView; reassigning.
Comment 2 James "Doc" Livingston 2006-07-11 10:13:50 UTC
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
Comment 3 Diego González 2006-07-23 18:48:29 UTC
there is something that i just noticed. If i click on the other views (artists) and the song view. Rhythmbox does not crash, however it does if there are two consecutive clicks on the album treeview.
Comment 4 James "Doc" Livingston 2006-07-24 12:08:18 UTC
Can you try repeating this passing "--g-fatal-warnings" as a command-line parameter, and getting a backtrace?
Comment 5 Diego González 2006-07-29 17:52:49 UTC
this is the gdb backtrace, however i'm unable to run rhythmbox under gdb with the --g-fatal-warnings because gdb itself is crashing for some reason.

  • #0 IA__g_object_unref
    at gobject.c line 1734
  • #1 rhythmdb_event_free
    at rhythmdb.c line 532
  • #2 rhythmdb_process_events
    at rhythmdb.c line 1850
  • #3 rhythmdb_idle_poll_events
    at rhythmdb.c line 1879
  • #4 g_timeout_dispatch
    at gmain.c line 3420
  • #5 g_main_dispatch
    at gmain.c line 2043
  • #6 IA__g_main_context_dispatch
    at gmain.c line 2594
  • #7 g_main_context_iterate
    at gmain.c line 2675
  • #8 IA__g_main_loop_run
    at gmain.c line 2879
  • #9 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0

I get this messages on the command line:

(rhythmbox:5775): GLib-GObject-WARNING **: invalid unclassed pointer in cast to `GObject'

(rhythmbox:5775): GLib-GObject-WARNING **: invalid unclassed pointer in cast to `GObject'

I have tried to comment the g_object_free on line 532 in the rhythmdb.c. With that change there are no more crashes, however i guess that rhythmbox leaks with it.
Comment 6 Jonathan Matthew 2006-08-12 01:13:07 UTC
This is another instance of the query model ref counting problem in bug 349601.


*** This bug has been marked as a duplicate of 349601 ***