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 128645 - Nautilus crashes when closing windows
Nautilus crashes when closing windows
Status: RESOLVED DUPLICATE of bug 128424
Product: nautilus
Classification: Core
Component: general
0.x.x [obsolete]
Other Linux
: Normal critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-12-06 07:00 UTC by Thomas Benson
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.5/2.6

Attachments
Crasher stack trace #1 (13.77 KB, text/plain)
2003-12-06 07:01 UTC, Thomas Benson 		Details
Crasher stack trace #2 (15.24 KB, text/plain)
2003-12-06 07:02 UTC, Thomas Benson 		Details

Description Thomas Benson 2003-12-06 07:00:20 UTC 
This is a recent CVS build using jhbuild.  Nautilus reports its version as
2.5.2.  If I open several windows and then start closing them, Nautilus
often crashes.  Sometimes it's after I close all of the windows, other
times as soon as I start to close them, and still other times it does not
crash.  I've crashed it about a dozen times in the past few minutes,
though, and the stack traces all look the same.

I will attach a few stack traces after opening the bug.
Comment 1 Thomas Benson 2003-12-06 07:01:37 UTC 
Created attachment 22144 [details]
Crasher stack trace #1
Comment 2 Thomas Benson 2003-12-06 07:02:10 UTC 
Created attachment 22145 [details]
Crasher stack trace #2
Comment 3 Thomas Benson 2003-12-06 07:09:30 UTC 
This looks somewhat similar to bug #128424, except that in that bug
the function g_type_check_instance_is_a is apparently reached.  I also
have another stack trace that is similar to these two but makes it to
g_type_check_instance_is_a that I will attach to bug #128424.  Both
sets of crashes occurred under similar circumstances and may be related.
Comment 4 Christophe Fergeau 2003-12-06 12:09:48 UTC 
They are the same imo since the line numbers are identical, marking as
a dup. Thanks for pointing that other bug out :)

*** This bug has been marked as a duplicate of 128424 ***
Comment 5 Thomas Benson 2003-12-06 17:17:31 UTC 
The only difference I noticed that caused me to open another bug was
that in these stack traces, the event variable passed to
gdk_event_translate is NULL whereas it is non-NULL in bug #128424.  It
seems to me that a NULL event would cause a crash at this line:

event->any.window = NULL;

in gdkevents-x11.c:796.  But, the stack trace indicates that it
crashes at 822.  I have no idea how it could dereference a NULL event
at the above line and not crash...