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

Bug #1813171 reported by Peter on 2019-01-24
This bug affects 2 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)

Bug Description

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
 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
 g_type_check_instance_is_fundamentally_a () at /usr/lib/x86_64-linux-gnu/
 g_object_ref () at /usr/lib/x86_64-linux-gnu/
 g_list_copy_deep () at /usr/lib/x86_64-linux-gnu/
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

Peter (platinum95) wrote :

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.

tags: added: regression-retracer

 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

Changed in nautilus (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
information type: Private → Public
summary: - nautilus crashed with SIGSEGV when working with large directory tree
+ nautilus crashed with SIGSEGV in nautilus_files_view_set_selection when
+ working with large directory tree
tags: added: focal
Launchpad Janitor (janitor) wrote :

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

Changed in nautilus (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers