nautilus crashed with SIGSEGV in _int_malloc()

Bug #1763969 reported by SiggiTron
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Expired
Medium
Unassigned

Bug Description

-

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: nautilus 1:3.26.3-0ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15
Uname: Linux 4.15.0-15-lowlatency x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat Apr 14 18:28:18 2018
ExecutablePath: /usr/bin/nautilus
InstallationDate: Installed on 2018-03-02 (43 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204)
ProcCmdline: /usr/bin/nautilus --gapplication-service
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=cs_CZ.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f8e59f8c20e <_int_malloc+3902>: cmp %rcx,0x28(%rdx)
 PC (0x7f8e59f8c20e) ok
 source "%rcx" ok
 destination "0x28(%rdx)" (0x00000022) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 _int_malloc (av=av@entry=0x7f8e5a2e2c40 <main_arena>, bytes=bytes@entry=2080) at malloc.c:4028
 _int_memalign (av=0x7f8e5a2e2c40 <main_arena>, alignment=1024, bytes=<optimized out>) at malloc.c:4694
 _mid_memalign (address=<optimized out>, bytes=1008, alignment=<optimized out>) at malloc.c:3314
 __posix_memalign (memptr=0x7ffd5be7cdb0, alignment=<optimized out>, size=1008) at malloc.c:5369
 ?? () 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
SiggiTron (siggitron) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 _int_malloc (av=av@entry=0x7f8e5a2e2c40 <main_arena>, bytes=bytes@entry=2080) at malloc.c:4028
 _int_memalign (av=0x7f8e5a2e2c40 <main_arena>, alignment=1024, bytes=<optimized out>) at malloc.c:4694
 _mid_memalign (address=<optimized out>, bytes=1008, alignment=1024) at malloc.c:3314
 __posix_memalign (memptr=memptr@entry=0x7ffd5be7cdb0, alignment=alignment@entry=1024, size=size@entry=1008) at malloc.c:5369
 allocator_memalign (memsize=1008, alignment=1024) at ../../../../glib/gslice.c:1411

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

information type: Private → Public
Changed in nautilus (Ubuntu):
status: New → 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.

Other bug subscribers

Remote bug watches

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