Bug 636829 – Delete Select Crash Combo

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 636829 - Delete Select Crash Combo


Summary:	Delete Select Crash Combo


Status:	RESOLVED DUPLICATE of bug 602500

Product:	nautilus
Classification:	Core
Component:	File and Folder Operations
Version:	2.30.x
Hardware:	Other Linux

Importance:	Normal minor
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2010-12-08 23:41 UTC by Rodro
Modified:	2010-12-09 04:01 UTC

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

Description Rodro 2010-12-08 23:41:18 UTC

I've marked this as minor and I'm reporting it because annoys me, but it's a crash so maybe is not so minor after all. Anyway, what happens is this:

1) Create a bunch of files (two is ok, maybe you can manage doing this with one, I don't know).

2) Delete the files (shift+del, enter) and rapidly press the up/down arrow keys so instead of the whole selection you mark a single file that is about to get deleted.

3) Nautilus disappears.

My guess is that when you select a file nautilus gets it as a pointer, when you delete the file it probably loses this reference as an attempt now to crash, but if you are really quick (doesn't need to be that quick for big files) you get the reference back at some kind of list|queue|stack. Once the file is deleted the reference is no longer valid and nautilus, unaware, dereferences it and thus crashes. Since I didn't take a look at the source code, I can't help much (and I really don't have time right now) but, if you don't have the man power, someone could give me a hint on where in the code the problem may be and I'll look into it in a few months (probably February).

Comment 1 Fabio Durán Verdugo 2010-12-09 04:00:16 UTC

yes I can confirm this bug.

add the traceback

Core was generated by `nautilus'.
Program terminated with signal 11, Segmentation fault.

+ Trace 225045

Thread 1 (Thread 1710)

#0 nautilus_file_peek_display_name
at nautilus-file.c line 3785
#1 nautilus_file_get_display_name
at nautilus-file.c line 3808
#2 selection_changed_callback
at nautilus-information-panel.c line 1129
#3 g_cclosure_marshal_VOID__VOID
at gmarshal.c line 79
#4 g_closure_invoke
at gclosure.c line 766
#5 signal_emit_unlocked_R
at gsignal.c line 3252
#6 g_signal_emit_valist
at gsignal.c line 2983
#7 g_signal_emit_by_name
at gsignal.c line 3077
#8 nautilus_window_report_selection_changed
at nautilus-window-manage-views.c line 116
#9 nautilus_window_info_report_selection_changed
at nautilus-window-info.c line 151
#10 fm_directory_view_send_selection_change
at fm-directory-view.c line 2377
#11 display_selection_info_idle_callback
at fm-directory-view.c line 2980
#12 g_idle_dispatch
at gmain.c line 4254
#13 g_main_dispatch
at gmain.c line 2149
#14 g_main_context_dispatch
at gmain.c line 2702
#15 g_main_context_iterate
at gmain.c line 2780
#16 g_main_loop_run
at gmain.c line 2988
#17 IA__gtk_main
at gtkmain.c line 1237
#18 main
at nautilus-main.c line 544

Comment 2 Fabio Durán Verdugo 2010-12-09 04:01:40 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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