nautilus crashed with SIGSEGV in _int_malloc()

Bug #1785122 reported by Mohammad Hizzani
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Expired
Medium
Unassigned

Bug Description

The nautilus closed all of a sudden

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: nautilus 1:3.26.3-0ubuntu4
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug 2 23:16:25 2018
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'196'
 b'org.gnome.nautilus.window-state' b'geometry' b"'960x1011+960+27'"
 b'org.gnome.nautilus.window-state' b'maximized' b'true'
 b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'standard'"
ProcCmdline: /usr/bin/nautilus --gapplication-service
SegvAnalysis:
 Segfault happened at: 0x7f34073e43c1 <_int_malloc+241>: mov 0x10(%rsi),%r9
 PC (0x7f34073e43c1) ok
 source "0x10(%rsi)" (0x7f33dc01cb0010) 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=0x7f33dc000020, bytes=bytes@entry=33) at malloc.c:3612
 _int_realloc (av=av@entry=0x7f33dc000020, oldp=oldp@entry=0x7f33dc042890, oldsize=oldsize@entry=32, nb=nb@entry=48) at malloc.c:4570
 __GI___libc_realloc (oldmem=0x7f33dc0428a0, 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:

Revision history for this message
Mohammad Hizzani (moh.hiz) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 _int_malloc (av=av@entry=0x7f33dc000020, bytes=bytes@entry=33) at malloc.c:3612
 _int_realloc (av=av@entry=0x7f33dc000020, oldp=oldp@entry=0x7f33dc042890, oldsize=oldsize@entry=32, nb=nb@entry=48) at malloc.c:4570
 __GI___libc_realloc (oldmem=0x7f33dc0428a0, bytes=bytes@entry=32) at malloc.c:3230
 g_realloc (mem=<optimized out>, n_bytes=32) at ../../../../glib/gmem.c:164
 g_array_maybe_expand (array=0x7f33ec019840, len=len@entry=1) at ../../../../glib/garray.c:794

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in nautilus (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
tags: added: cosmic
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in nautilus (Ubuntu):
status: New → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

Changed in nautilus (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.]

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.