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 128424 - Crash in glib: g_type_check_instance_is_a() after closing last window (nautilus-2.5.2, glib-2.3.0)
Crash in glib: g_type_check_instance_is_a() after closing last window (nautil...
Status: RESOLVED DUPLICATE of bug 117579
Product: nautilus
Classification: Core
Component: general
0.x.x [obsolete]
Other Linux
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 128645 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2003-12-03 08:36 UTC by Håkon Innerdal
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
stack trace (16.21 KB, text/plain)
2003-12-06 07:15 UTC, Thomas Benson 		Details

Description Håkon Innerdal 2003-12-03 08:36:11 UTC 
Description of Problem:
Nautilus crashes after closing the last opened
window. That is, open lots of windows, close them,
and after closing the last one, nautilus crashes.
(not necessarily nautilus fault, glib? see
stack-trace)

Steps to reproduce the problem:
1. Open home folder
2. close it
3. crash


How often does this happen? 
Every time.

Additional Information:
(Listing (hopefully) related version-numbers
Compiled from garnome 2.28.2
nautilus 2.5.2
glib-2.3.0

Running on fedora core 1

Stack:

+ Trace 42270

  • #0 g_type_check_instance_is_a
    at gtype.c line 3104
  • #1 gdk_event_translate
    at gdkevents-x11.c line 822
  • #2 _gdk_events_queue
    at gdkevents-x11.c line 2028
  • #3 gdk_event_dispatch
    at gdkevents-x11.c line 2088
  • #4 g_main_dispatch
    at gmain.c line 1752
  • #5 g_main_context_dispatch
    at gmain.c line 2300
  • #6 g_main_context_iterate
    at gmain.c line 2381
  • #7 g_main_loop_run
    at gmain.c line 2601
  • #8 gtk_main
    at gtkmain.c line 1124
  • #9 main
  • #1 gdk_event_translate
    at gdkevents-x11.c line 822 
$6 = {parent_instance = {g_type_instance =
{g_class = 0x80e1f60},
    ref_count = 1, qdata = 0x82b8660},
queued_events = 0x83762dc,
  queued_tail = 0x83762dc, button_click_time =
{86291312, 86291112},
  button_window = {0x83e8108, 0x83e8108},
button_number = {1, 1},
  double_click_time = 400, core_pointer = 0x80e6878,
  pointer_hooks = 0x4f1db170, closed = 0}
(gdb)


Please query me if additional info is needed.
Comment 1 Thomas Benson 2003-12-06 07:14:05 UTC 
I think I'm seeing the same or at least a similar bug that I reported
in bug #128645.  I will attach a stack trace here that seems to be
very similar to above.
Comment 2 Thomas Benson 2003-12-06 07:15:16 UTC 
Created attachment 22146 [details]
stack trace
Comment 3 Christophe Fergeau 2003-12-06 12:09:46 UTC 
*** Bug 128645 has been marked as a duplicate of this bug. ***
Comment 4 Christophe Fergeau 2003-12-06 12:12:12 UTC 
Is it still happening with newest GTK+ ? (either CVS HEAD, or 2.3.1
which will be released next week hopefully)
Comment 5 Thomas Benson 2003-12-06 17:45:08 UTC 
I updated to CVS versions of both GTK+ and Nautilus and still get this
crash (actually, I get stack traces like those in bug #128424, which
I'm not sure are identical, although they may be -- I added a comment
to that bug about that).
Comment 6 Elijah Newren 2003-12-08 04:57:59 UTC 
Doing some basic fixes: GNOMEVER2.0 should be GNOMEVER2.5, this should
be priority->high & severity->critical (it's a crasher), I'm adding
the STACKTRACE keyword and the bugsquad keyword as well.  Finally, I'm
setting the version appropriately.
Comment 7 Soren Sandmann Pedersen 2003-12-09 03:31:52 UTC 
This bug is a duplicate of 116719. Expect lots of duplicates as people
start testing nautilus with gtk+ HEAD.


*** This bug has been marked as a duplicate of 116719 ***
Comment 8 Soren Sandmann Pedersen 2003-12-09 16:38:29 UTC 
Reopening to duplicate against right bug
Comment 9 Soren Sandmann Pedersen 2003-12-09 16:39:43 UTC 

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