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:
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.