gnome-control-center crashed with SIGSEGV in thread_memory_magazine2_free()

Bug #1237899 reported by Yuriy Padlyak
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

-

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: gnome-control-center 1:3.6.3-0ubuntu41
ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
Uname: Linux 3.11.0-11-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.12.5-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Fri Oct 4 16:41:06 2013
ExecutablePath: /usr/bin/gnome-control-center
ExecutableTimestamp: 1380729441
MarkForUpload: True
ProcCmdline: gnome-control-center region layouts
ProcCwd: /home/yura
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
 LANGUAGE=uk_UA:en
 PATH=(custom, user)
 LANG=uk_UA.UTF-8
SegvAnalysis:
 Segfault happened at: 0xb6cf5203 <g_slice_free1+451>: movl $0x0,0x4(%ebp)
 PC (0xb6cf5203) ok
 source "$0x0" ok
 destination "0x4(%ebp)" (0x00000047) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 g_slice_free1 () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
Title: gnome-control-center crashed with SIGSEGV in g_slice_free1()
UpgradeStatus: Upgraded to saucy on 2013-10-04 (0 days ago)
UserGroups: adm admin cdrom debian-tor dialout dip fax floppy fuse libvirtd lpadmin plugdev sambashare tape video
usr_lib_gnome-control-center:
 activity-log-manager 0.9.7-0ubuntu4
 deja-dup 27.3.1-0ubuntu1
 gnome-control-center-datetime 13.10.0+13.10.20130930-0ubuntu1
 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1
 gnome-control-center-unity 1.3daily13.06.19~13.04-0ubuntu1

Revision history for this message
Yuriy Padlyak (gneeot) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 thread_memory_magazine2_free (tmem=<optimized out>, mem=0x43, ix=1) at /build/buildd/glib2.0-2.38.0/./glib/gslice.c:861
 g_slice_free1 (mem_size=mem_size@entry=16, mem_block=0x43) at /build/buildd/glib2.0-2.38.0/./glib/gslice.c:1110
 free_sizes (sizes=<optimized out>) at /build/buildd/gtk+3.0-3.8.4/./gtk/gtksizerequestcache.c:40
 _gtk_size_request_cache_free (cache=cache@entry=0x9f2a6bc) at /build/buildd/gtk+3.0-3.8.4/./gtk/gtksizerequestcache.c:53
 _gtk_size_request_cache_clear (cache=0x9f2a6bc) at /build/buildd/gtk+3.0-3.8.4/./gtk/gtksizerequestcache.c:61

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-control-center (Ubuntu):
importance: Undecided → Medium
summary: - gnome-control-center crashed with SIGSEGV in g_slice_free1()
+ gnome-control-center crashed with SIGSEGV in
+ thread_memory_magazine2_free()
tags: removed: need-i386-retrace
information type: Private → Public
Revision history for this message
Sebastien Bacher (seb128) wrote :

The bug hasn't seen any activity in years and there has been no recent similar reports, the code also changed quite a lot since and it's likely the issue doesn't exist anymore. Closing, feel free to open a new report if you still get problems in recent Ubuntu versions

Changed in gnome-control-center (Ubuntu):
status: New → Invalid
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.