*** This bug is a duplicate of bug 1785122 ***
    https://bugs.launchpad.net/bugs/1785122

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 #1785122, 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.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1790284/+attachment/5183409/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1790284/+attachment/5183411/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1790284/+attachment/5183415/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1790284/+attachment/5183416/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1790284/+attachment/5183417/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1790284/+attachment/5183418/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1790284/+attachment/5183419/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1785122
   nautilus crashed with SIGSEGV in _int_malloc()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1790284

Title:
  nautilus crashed with SIGSEGV in _int_malloc()

Status in nautilus package in Ubuntu:
  New

Bug description:
  I don't know more details.I noticed the disk LED flashed frequently.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: nautilus 1:3.26.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
  Uname: Linux 4.17.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep  1 18:50:20 2018
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.window-state' b'geometry' b"'890x529+26+23'"
  InstallationDate: Installed on 2018-08-13 (18 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180723)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  SegvAnalysis:
   Segfault happened at: 0x7f692700b354 <_int_malloc+132>:      mov    
0x10(%rcx),%r9
   PC (0x7f692700b354) ok
   source "0x10(%rcx)" (0x7f6900010ea010) not located in a known VMA region 
(needed readable region)!
   destination "%r9" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   _int_malloc (av=av@entry=0x7f6900000020, bytes=bytes@entry=33) at 
malloc.c:3584
   _int_realloc (av=av@entry=0x7f6900000020, oldp=oldp@entry=0x7f6900010fc0, 
oldsize=oldsize@entry=32, nb=nb@entry=48) at malloc.c:4570
   __GI___libc_realloc (oldmem=0x7f6900010fd0, bytes=32) at malloc.c:3230
   g_realloc () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: nautilus crashed with SIGSEGV in _int_malloc()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1790284/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to