Bug 77331 – nautilus crash when closing a window that is updating

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 77331 - nautilus crash when closing a window that is updating


Summary:	nautilus crash when closing a window that is updating


Status:	RESOLVED FIXED

Product:	nautilus
Classification:	Core
Component:	File and Folder Operations
Version:	2.2.x
Hardware:	Other other

Importance:	High critical
Target Milestone:	2.0.x
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Duplicates:	77332 77333 77334 78772 92521 105955 112237 113059 (view as bug list)
Depends on:
Blocks:

Reported:	2002-04-02 08:32 UTC by Christoph Hippchen
Modified:	2004-12-22 21:47 UTC

See Also:
GNOME target:	---
GNOME version:	2.0

Description Christoph Hippchen 2002-04-02 08:32:49 UTC

Description of Problem:
nautilus crashes when closing a window that is updating

Steps to reproduce the problem:
1. Open a nautilus window to view a directory
2. Move a mess of files via a term
3. Close window as nautilus is updating 
Always reproducible here

Actual Results:
Crash

Expected Results:
Window closes


Debugging Information:

[New Thread 1024 (LWP 2147)]
[New Thread 2049 (LWP 2167)]
[New Thread 1026 (LWP 2168)]
[New Thread 2051 (LWP 2169)]
[New Thread 3076 (LWP 2172)]
[New Thread 4101 (LWP 3648)]
[New Thread 5126 (LWP 3649)]
[New Thread 6151 (LWP 3650)]
[New Thread 7176 (LWP 3651)]
[New Thread 8201 (LWP 3652)]
0x410d2c89 in __wait4 () from /lib/libc.so.6

+ Trace 20198

Thread 1 (Thread 1024 (LWP 2147))

#0 __wait4
from /lib/libc.so.6
#1 __DTOR_END__
from /lib/libc.so.6
#2 waitpid
at wrapsyscall.c line 172
#3 libgnomeui_segv_handle
at gnome-ui-init.c line 593
#4 pthread_sighandler
at signals.c line 97
#5 <signal handler called>
#6 g_type_check_instance_cast
at gtype.c line 2639
#7 new_files_callback
at nautilus-directory-async.c line 1436
#8 dispatch_get_file_info_callback
at gnome-vfs-job.c line 269
#9 dispatch_job_callback
at gnome-vfs-job.c line 550
#10 g_idle_dispatch
at gmain.c line 3129
#11 g_main_dispatch
at gmain.c line 1617
#12 g_main_context_dispatch
at gmain.c line 2161
#13 g_main_context_iterate
at gmain.c line 2242
#14 g_main_loop_run
at gmain.c line 2462
#15 gtk_main
at gtkmain.c line 912
#16 main
at nautilus-main.c line 263
#17 __libc_start_main
at ../sysdeps/generic/libc-start.c line 129
#0 __wait4
from /lib/libc.so.6
#0 __wait4
from /lib/libc.so.6
#1 __DTOR_END__
from /lib%

Comment 1 John Fleck 2002-04-02 13:57:13 UTC

*** Bug 77332 has been marked as a duplicate of this bug. ***

Comment 2 John Fleck 2002-04-02 13:57:33 UTC

*** Bug 77333 has been marked as a duplicate of this bug. ***

Comment 3 John Fleck 2002-04-02 13:57:54 UTC

*** Bug 77334 has been marked as a duplicate of this bug. ***

Comment 4 Heath Harrelson 2002-04-15 20:36:49 UTC

*** Bug 78772 has been marked as a duplicate of this bug. ***

Comment 5 Damon Chaplin 2002-04-23 19:28:21 UTC

the gnomevfs calls to get the file infos are not cancelled like
the other gnomevfs calls in nautilus_directory_cancel().
See directory->details->get_file_infos_in_progress.

So we need to cancel them??

Comment 6 Luis Villa 2002-05-01 11:08:23 UTC

repeated crash->2.0.0

Comment 7 Alexander Larsson 2002-05-13 03:55:15 UTC

I haven't studied this in detail, but it's entierly possible that the
fix for bug 75617 fixed this problem too. Does anyone still see it?

Comment 8 Luis Villa 2002-05-22 21:53:58 UTC

I can no longer reproduce; marking closed. Cristoph, if you can still
reproduce this, please reopen.

Comment 9 Luis Villa 2002-09-11 20:50:37 UTC

*** Bug 92521 has been marked as a duplicate of this bug. ***

Comment 10 Luis Villa 2002-09-11 20:51:26 UTC

Looks like it isn't /completely/ gone, though I'm going to remove the
2.0.0 keyword since since release we've had only one report and it was
clearly frequent before.

Comment 11 John Fleck 2003-02-13 14:05:48 UTC

*** Bug 105955 has been marked as a duplicate of this bug. ***

Comment 12 John Fleck 2003-05-05 02:45:43 UTC

*** Bug 112237 has been marked as a duplicate of this bug. ***

Comment 13 mwehner 2003-09-26 10:18:47 UTC

*** Bug 113059 has been marked as a duplicate of this bug. ***

Comment 14 mwehner 2003-09-26 10:21:38 UTC

Setting version to 2.2.x since the last duplicate was reported with 2.2.1.

Comment 15 mwehner 2003-10-12 06:36:46 UTC

Since this hasn't been reported for versions > 2.2.x (and only once
for 2.2.x, all other reports are from 2.0.x), I think this has been
fixed and are marking it as such.