Bug 84910 – Crash after adding new folder to Applications menu

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 84910 - Crash after adding new folder to Applications menu


Summary:	Crash after adding new folder to Applications menu


Status:	RESOLVED FIXED

Product:	nautilus
Classification:	Core
Component:	general
Version:	unspecified
Hardware:	Other other

Importance:	High critical
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2002-06-11 17:59 UTC by Steve Tyler
Modified:	2004-12-22 21:47 UTC

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

Description Steve Tyler 2002-06-11 18:03:57 UTC

Package: nautilus
Severity: critical
Version: 2.0.0
Synopsis: Crash after adding new folder to Applications menu
Bugzilla-Product: nautilus
Bugzilla-Component: general
BugBuddy-GnomeVersion: 2.0 (2.0.0)

Description:
Description of Problem:


Steps to reproduce the problem:
1. Go, Start-Here, Applications
2. Create a folder, type in a name
3. Name is ignored, nautilus appears to hang, but will eventually crash

Actual Results:


Expected Results:
Set the name of the folder properly, and not crash

How often does this happen?


Additional Information:




Debugging Information:

Backtrace was generated from '/usr/bin/nautilus'

[New Thread 1024 (LWP 1480)]
[New Thread 2049 (LWP 1483)]
[New Thread 1026 (LWP 1484)]
[New Thread 2051 (LWP 1485)]
[New Thread 3076 (LWP 1486)]
0x420b4769 in wait4 () from /lib/i686/libc.so.6

+ Trace 23645

Thread 1 (Thread 1024 (LWP 1480))

#0 wait4
from /lib/i686/libc.so.6
#1 __DTOR_END__
from /lib/i686/libc.so.6
#2 waitpid
from /lib/i686/libpthread.so.0
#3 libgnomeui_segv_handle
at gnome-ui-init.c line 620
#4 pthread_sighandler
from /lib/i686/libpthread.so.0
#5 <signal handler called>
#6 g_logv





------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-06-11 14:03 -------

Reassigning to the default owner of the component, nautilus-maint@bugzilla.gnome.org.

Comment 1 Luis Villa 2002-06-12 03:56:02 UTC

Michael: Could you take a quick look at this? I think it might be a
better/more reliable way to reproduce 74189...

Comment 2 Dave Camp 2002-06-14 20:47:29 UTC


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

Comment 3 Damon Chaplin 2002-06-21 18:03:01 UTC

Here's a trace of the hang. I'm tempted to reopen this as the hang
is possibly a separate issue to the crash.


(gdb) thread apply all bt

+ Trace 24139

Thread 7 (Thread 5126 (LWP 1481))

#0 __sigsuspend
at ../sysdeps/unix/sysv/linux/sigsuspend.c line 45
#1 __pthread_wait_for_restart_signal
at pthread.c line 969
#2 pthread_cond_wait
at restart.h line 34
#3 gnome_vfs_thread_pool_wait_for_work
at gnome-vfs-thread-pool.c line 155
#4 thread_entry
at gnome-vfs-thread-pool.c line 176
#5 pthread_start_thread
at manager.c line 284

Thread 6 (Thread 4101 (LWP 1480))

#0 __sigsuspend
at ../sysdeps/unix/sysv/linux/sigsuspend.c line 45
#1 __pthread_wait_for_restart_signal
at pthread.c line 969
#2 pthread_cond_wait
at restart.h line 34
#3 gnome_vfs_thread_pool_wait_for_work
at gnome-vfs-thread-pool.c line 155
#4 thread_entry
at gnome-vfs-thread-pool.c line 176
#5 pthread_start_thread
at manager.c line 284

Thread 5 (Thread 3076 (LWP 1479))

#0 __sigsuspend
at ../sysdeps/unix/sysv/linux/sigsuspend.c line 45
#1 __pthread_wait_for_restart_signal
at pthread.c line 969
#2 __pthread_alt_lock
at restart.h line 34
#3 __pthread_mutex_lock
at mutex.c line 120
#4 get_vfolder_info
at vfolder-desktop-method.c line 3410
#5 do_get_file_info
at vfolder-desktop-method.c line 5003
#6 gnome_vfs_get_file_info_uri_cancellable
at gnome-vfs-cancellable-ops.c line 168
#7 execute_get_file_info
at gnome-vfs-job.c line 1262
#8 gnome_vfs_job_execute
at gnome-vfs-job.c line 1590
#9 thread_routine
at gnome-vfs-job-slave.c line 62
#10 thread_entry
at gnome-vfs-thread-pool.c line 180
#11 pthread_start_thread
at manager.c line 284

Thread 4 (Thread 2051 (LWP 1476))

#0 __sigsuspend
at ../sysdeps/unix/sysv/linux/sigsuspend.c line 45
#1 __pthread_wait_for_restart_signal
at pthread.c line 969
#2 pthread_cond_wait
at restart.h line 34
#3 gnome_vfs_thread_pool_wait_for_work
at gnome-vfs-thread-pool.c line 155
#4 thread_entry
at gnome-vfs-thread-pool.c line 176
#5 pthread_start_thread
at manager.c line 284

Thread 3 (Thread 1026 (LWP 1475))

#0 __sigsuspend
at ../sysdeps/unix/sysv/linux/sigsuspend.c line 45
#1 __pthread_wait_for_restart_signal
at pthread.c line 969
#2 __pthread_alt_lock
at restart.h line 34
#3 __pthread_mutex_lock
at mutex.c line 120
#4 ensure_folder
at vfolder-desktop-method.c line 976
#5 try_free_file_monitors_create_files_unlocked
at vfolder-desktop-method.c line 2824
#6 rescan_monitors
at vfolder-desktop-method.c line 3000
#7 vfolder_info_reload_unlocked
at vfolder-desktop-method.c line 3241
#8 vfolder_info_recheck
at vfolder-desktop-method.c line 3301
#9 get_vfolder_info_unlocked
at vfolder-desktop-method.c line 3332
#10 get_vfolder_info
at vfolder-desktop-method.c line 3411
#11 do_move
at vfolder-desktop-method.c line 5534
#12 do_set_file_info
at vfolder-desktop-method.c line 5826
#13 gnome_vfs_set_file_info_cancellable
at gnome-vfs-cancellable-ops.c line 417
#14 execute_set_file_info
at gnome-vfs-job.c line 1294
#15 gnome_vfs_job_execute
at gnome-vfs-job.c line 1593
#16 thread_routine
at gnome-vfs-job-slave.c line 62
#17 thread_entry
at gnome-vfs-thread-pool.c line 180
#18 pthread_start_thread
at manager.c line 284

Thread 1 (Thread 1024 (LWP 1471))

#0 __sigsuspend
at ../sysdeps/unix/sysv/linux/sigsuspend.c line 45
#1 __pthread_wait_for_restart_signal
at pthread.c line 969
#2 __pthread_alt_lock
at restart.h line 34
#3 __pthread_mutex_lock
at mutex.c line 120
#4 get_vfolder_info
at vfolder-desktop-method.c line 3410
#5 do_get_file_info
at vfolder-desktop-method.c line 5003
#6 gnome_vfs_get_file_info_uri_cancellable
at gnome-vfs-cancellable-ops.c line 168
#7 gnome_vfs_get_file_info_uri
at gnome-vfs-ops.c line 302
#8 gnome_vfs_get_file_info
at gnome-vfs-ops.c line 275
#9 get_link_style_for_local_file
at nautilus-link.c line 80
#10 nautilus_link_local_get_additional_text
at nautilus-link.c line 192
#11 fm_icon_container_get_icon_text
at fm-icon-container.c line 204
#12 nautilus_icon_container_get_icon_text
at nautilus-icon-container.c line 3789
#13 nautilus_icon_container_update_icon
at nautilus-icon-container.c line 3876
#14 nautilus_icon_container_request_update_all
at nautilus-icon-container.c line 4155
#15 fm_icon_view_emblems_changed
at fm-icon-view.c line 1998
#16 file_changed_callback
at fm-directory-view.c line 5039
#17 g_cclosure_marshal_VOID__VOID
#18 g_closure_invoke
at gclosure.c line 437
#19 signal_emit_unlocked_R
at gsignal.c line 2341
#20 g_signal_emit_valist
at gsignal.c line 2100
#21 g_signal_emit
at gsignal.c line 2144
#22 nautilus_file_emit_changed
at nautilus-file.c line 4740
#23 nautilus_directory_emit_change_signals
at nautilus-directory.c line 723
#24 call_files_changed_common
at nautilus-directory.c line 833
#25 call_files_changed_unref_free_list
at nautilus-directory.c line 852
#26 g_hash_table_foreach
at ghash.c line 559
#27 nautilus_directory_notify_files_changed
at nautilus-directory.c line 993
#28 nautilus_file_changes_consume_changes
at nautilus-file-changes-queue.c line 452
#29 call_consume_changes_idle_cb
at nautilus-monitor.c line 90
#30 g_idle_dispatch
at gmain.c line 3129
#31 g_main_dispatch
at gmain.c line 1617
#32 g_main_context_dispatch
at gmain.c line 2161
#33 g_main_context_iterate
at gmain.c line 2242
#34 g_main_loop_run
at gmain.c line 2462
#35 gtk_main
at gtkmain.c line 936
#36 main
at nautilus-main.c line 263
#37 __libc_start_main
at ../sysdeps/generic/libc-start.c line 129

Comment 4 Michael Meeks 2002-06-27 17:28:16 UTC

You're right - this hang is a separate bug - looks like a dealock in
the interesting code in the vfolder backend; [ the 2nd trace looks
highly suspicious - calling a method that does a lock from an
_unlocked method ].

Threads Rock ! anyway, I'm on the case ...

Comment 5 Michael Meeks 2002-06-28 08:55:53 UTC

Committed the deadlock fix - pretty mindless.