nautilus crashed with SIGSEGV in nautilus_files_view_set_selection when working with large directory tree

[Peter]

Was working with a relatively large directory tree (machine learning dataset of images, separated into folders). Nautilus froze up and crashed. Unsure if it's related to the large directory tree but I have found it getting sluggish in similar places

ProblemType: Crash
DistroRelease: Ubuntu 19.04
Package: nautilus 1:3.30.5-1ubuntu1
Uname: Linux 5.0.0-050000rc1-lowlatency x86_64
ApportVersion: 2.20.10-0ubuntu19
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 24 11:25:26 2019
ExecutablePath: /usr/bin/nautilus
InstallationDate: Installed on 2018-11-28 (56 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
ProcCmdline: /usr/bin/nautilus --gapplication-service
SegvAnalysis:
 Segfault happened at: 0x7feb96a05ac5 <g_type_check_instance_is_fundamentally_a+5>: mov (%rdi),%rax
 PC (0x7feb96a05ac5) ok
 source "(%rdi)" (0x00000001) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 g_type_check_instance_is_fundamentally_a () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_ref () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_list_copy_deep () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 ()
 ()
Title: nautilus crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
UpgradeStatus: Upgraded to disco on 2019-01-10 (13 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users
usr_lib_nautilus:

[Apport retracing service (apport)]

This crash has the same stack trace characteristics as bug #1713581. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.

[Apport retracing service (apport)]

StacktraceTop:
 g_type_check_instance_is_fundamentally_a (type_instance=type_instance@entry=0x1, fundamental_type=fundamental_type@entry=80) at ../../../../gobject/gtype.c:4023
 g_object_ref (_object=0x1) at ../../../../gobject/gobject.c:3212
 g_list_copy_deep (list=list@entry=0x55e7c95b2ac0, func=0x7feb969e6880 <g_object_ref>, user_data=user_data@entry=0x0) at ../../../../glib/glist.c:685
 nautilus_files_view_set_selection (nautilus_files_view=<optimized out>, selection=0x55e7c95b2ac0) at ../src/nautilus-files-view.c:3162
 load_new_location (self=<optimized out>, location=0x55e7c8ce80c0, selection=0x55e7c95b2ac0, file_to_activate=0x0, tell_current_content_view=<optimized out>, tell_new_content_view=<optimized out>) at ../src/nautilus-window-slot.c:2141

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Khalid Abu Shawarib (khalid-shawarib)]

Most likely to be this: https://gitlab.gnome.org/GNOME/nautilus/-/issues/3036

There's a fix, but it's hard to verify as this bug is very fickle in the scenario described by this report. There's only one known case where it's consistently reproducible, which is to open 2 files with nautilus in the "Open With..." dialog.

Backtrace on 46.1:
[Current thread is 1 (Thread 0x7f72ee96bd00 (LWP 451947))]
(gdb) bt
#0 0x00007f72f34c5d59 in g_type_check_instance_is_fundamentally_a (type_instance=0x732d7265646c6f66, fundamental_type=0x50)
    at ../../../gobject/gtype.c:4151
#1 0x00007f72f34aa959 in g_object_ref (_object=0x732d7265646c6f66) at ../../../gobject/gobject.c:4199
#2 0x00007f72f444c7a9 in g_list_copy_deep
    (list=0x55cb23ebebe0 = {...}, func=0x7f72f34aa930 <g_object_ref>, user_data=user_data@entry=0x0)
    at ../../../glib/glist.c:680
#3 0x000055cb232a9641 in nautilus_files_view_set_selection (nautilus_files_view=<optimized out>, selection=<optimized out>)
    at ../src/nautilus-files-view.c:3251
#4 0x000055cb23257d7e in load_new_location
    (self=self@entry=0x55cb241e59f0, location=<optimized out>, selection=0x55cb23ebebe0 = {...}, file_to_activate=0x0, tell_current_content_view=tell_current_content_view@entry=0, tell_new_content_view=tell_new_content_view@entry=1)
    at ../src/nautilus-window-slot.c:2045
#5 0x000055cb2325d21c in setup_view (view=<optimized out>, self=0x55cb241e59f0) at ../src/nautilus-window-slot.c:1982
#6 got_file_info_for_view_selection_callback (file=0x55cb23ce04b0, callback_data=0x55cb241e59f0)
    at ../src/nautilus-window-slot.c:1870
#7 0x000055cb232d407a in call_ready_callbacks_at_idle (callback_data=0x55cb23ce01c0)
    at ../src/nautilus-directory-async.c:1812
#8 0x00007f72f445048e in g_main_dispatch (context=0x55cb238e5d30) at ../../../glib/gmain.c:3344
#9 0x00007f72f44af717 in g_main_context_dispatch_unlocked (context=0x55cb238e5d30) at ../../../glib/gmain.c:4152
#10 g_main_context_iterate_unlocked.isra.0
    (context=context@entry=0x55cb238e5d30, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>)
    at ../../../glib/gmain.c:4217
#11 0x00007f72f444fa53 in g_main_context_iteration (context=context@entry=0x55cb238e5d30, may_block=may_block@entry=1)
    at ../../../glib/gmain.c:4282
#12 0x00007f72f35d388d in g_application_run
    (application=application@entry=0x55cb238d0b30, argc=argc@entry=2, argv=argv@entry=0x7ffd95a9da18)
    at ../../../gio/gapplication.c:2712
#13 0x000055cb2324631d in main (argc=2, argv=0x7ffd95a9da18) at ../src/nautilus-main.c:78