nautilus crashed with SIGSEGV in magazine_cache_trim()

Bug #1420912 reported by J
26
This bug affects 3 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

none

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: nautilus 1:3.14.2-0ubuntu3
ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
Uname: Linux 3.18.0-13-generic x86_64
ApportVersion: 2.16.1-0ubuntu2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Wed Feb 11 16:13:05 2015
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'smaller'"
 b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']"
InstallationDate: Installed on 2014-10-24 (110 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
ProcCmdline: nautilus --new-window
ProcEnviron:
 LANGUAGE=es_UY:es
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=es_UY.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7ff6a80e9a21: mov %rdi,0x8(%r9)
 PC (0x7ff6a80e9a21) ok
 source "%rdi" ok
 destination "0x8(%r9)" (0x00000008) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_slice_free1 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_variant_unref () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_slice_free1()
UpgradeStatus: Upgraded to vivid on 2015-01-05 (37 days ago)
UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo
usr_lib_nautilus:
 brasero 3.12.0-0ubuntu2
 evince 3.14.1-0ubuntu3
 file-roller 3.14.2-0ubuntu4
 gnome-terminal 3.14.2-0ubuntu1
 nautilus-share 0.7.3-1ubuntu5

Revision history for this message
J (jsartti) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 magazine_cache_trim (allocator=0x7ff6a8392380 <allocator>, stamp=2044180073, ix=2) at /build/buildd/glib2.0-2.43.3/./glib/gslice.c:649
 magazine_cache_push_magazine (ix=2, magazine_chunks=<optimized out>, count=34) at /build/buildd/glib2.0-2.43.3/./glib/gslice.c:710
 thread_memory_magazine2_unload (ix=<optimized out>, tmem=<optimized out>) at /build/buildd/glib2.0-2.43.3/./glib/gslice.c:809
 g_slice_free1 (mem_size=<optimized out>, mem_block=0x1f2d0f0) at /build/buildd/glib2.0-2.43.3/./glib/gslice.c:1094
 g_bytes_unref (bytes=<optimized out>) at /build/buildd/glib2.0-2.43.3/./glib/gbytes.c:310

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
summary: - nautilus crashed with SIGSEGV in g_slice_free1()
+ nautilus crashed with SIGSEGV in magazine_cache_trim()
tags: removed: need-amd64-retrace
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 :

The bug didn't get activity/new duplicates for some years and the nautilus code saw quite some changes since which probably deprecated the issue so closing it. If it's still a problem in recent Ubuntu/nautilus version please submit a new report

Changed in nautilus (Ubuntu):
status: Confirmed → Invalid
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.