gnome-terminal-server crashed with SIGSEGV in magazine_cache_trim()

Bug #1435383 reported by Dan
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
gnome-terminal (Ubuntu)
Expired
Medium
Unassigned

Bug Description

...

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: gnome-terminal 3.14.2-0ubuntu2
ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
Uname: Linux 3.19.0-9-generic x86_64
ApportVersion: 2.16.2-0ubuntu4
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Mar 23 17:21:23 2015
ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
InstallationDate: Installed on 2015-01-16 (66 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
ProcCmdline: /usr/lib/gnome-terminal/gnome-terminal-server
SegvAnalysis:
 Segfault happened at: 0x7eff59c587f1: mov %rdi,0x8(%r9)
 PC (0x7eff59c587f1) ok
 source "%rdi" ok
 destination "0x8(%r9)" (0x00000008) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gnome-terminal
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
 ?? () from /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0
 g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-terminal-server crashed with SIGSEGV in g_slice_free1()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo

Revision history for this message
Dan (danutz-1200) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 magazine_cache_trim (allocator=0x7eff59f01380 <allocator>, stamp=1194941149, ix=2) at /build/buildd/glib2.0-2.43.92/./glib/gslice.c:649
 magazine_cache_push_magazine (ix=2, magazine_chunks=<optimized out>, count=34) at /build/buildd/glib2.0-2.43.92/./glib/gslice.c:710
 thread_memory_magazine2_unload (ix=<optimized out>, tmem=<optimized out>) at /build/buildd/glib2.0-2.43.92/./glib/gslice.c:809
 g_slice_free1 (mem_size=<optimized out>, mem_block=0xf39f80) at /build/buildd/glib2.0-2.43.92/./glib/gslice.c:1094
 pango_context_finalize (object=0xe01640) at /build/buildd/pango1.0-1.36.8/./pango/pango-context.c:120

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 gnome-terminal (Ubuntu):
importance: Undecided → Medium
summary: - gnome-terminal-server crashed with SIGSEGV in g_slice_free1()
+ gnome-terminal-server 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 gnome-terminal (Ubuntu):
status: New → Confirmed
Revision history for this message
Paul White (paulw2u) wrote :

We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.

Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.

Do you still see a problem related to the one that was reported in a currently supported version of Ubuntu? Please let us know if you do and in which version otherwise this report can be left to expire in approximately 60 days time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]

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

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

Changed in gnome-terminal (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.