nautilus crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()

[Tolga Senel]

i had 4 files pages open and i was deleting and transferring files from my external hard drive to relevant folders in my laptop ssd. suddenly all pages crushed.

ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: nautilus 1:3.36.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu21
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 3 14:40:51 2020
ExecutablePath: /usr/bin/nautilus
InstallationDate: Installed on 2020-03-26 (7 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200325)
ProcCmdline: /usr/bin/nautilus --gapplication-service
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANGUAGE=en_GB:en
 LANG=en_GB.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7fb334885671 <g_type_check_instance_is_fundamentally_a+17>: mov (%rax),%rax
 PC (0x7fb334885671) ok
 source "(%rax)" (0x56415741fa1e0ff3) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 g_type_check_instance_is_fundamentally_a () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_ref () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_list_copy_deep () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ()
 ()
Title: nautilus crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip input lpadmin lxd plugdev sambashare sudo
separator:

usr_lib_nautilus:

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1813171, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.