compiz crashed with SIGSEGV in _int_malloc()

Bug #923049 reported by Daniel Clem
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Nux
New
Undecided
Unassigned
Unity
New
Undecided
Unassigned
nux (Ubuntu)
Confirmed
Critical
Unassigned

Bug Description

Am Running off of a 4 GB USB flash drive. I was changing "Image Loading" check boxes. At the moment of the crash I had just clicked to enable the SVG checkbox.

P.S. Please don't remove CCSM from the Repos?? Yes It can cause crashes such as this and in other cases and flat out break systems depending on what you change. But why not have the main developer fix the breakages, or put the options that cause the breaks into an "Advanced Users Only" page or tab? I

 really love tweaking these settings to MY preferences. Such as increasing the animations timing. Cause 120 ms is BARELY enough time to even notice any animation. Much less truely appreciate it for adding to the flare of the system. I also am in Love with the ADD helper plugin. I don't paticularly have ADD, but it does help to focus on what I'm doing, and I enjoy being able to see all the running and open applications behind my currently selected one, as well as the high res wallpaper.

If you do decide to take out CCSM....PLEASE!!!!!! Have consideration of your users to either build the top plugins into the Settings application. OR put a bounty out to have the devs of Ubuntu Tweak or MyUnity to build all more advanced Compiz tweaking options into their apps. As loosing easy access to CCSM will just plain suck, as I have no experience or desire to compile CCSM from source after its removed from the repos.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: libnux-1.0-0 1.16.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-15.26-generic 3.0.13
Uname: Linux 3.0.0-15-generic i686
ApportVersion: 1.23-0ubuntu4
Architecture: i386
CasperVersion: 1.287.1
Date: Sat Jan 28 13:03:26 2012
ExecutablePath: /usr/bin/compiz
LiveMediaBuild: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
ProcCmdline: compiz
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x489f71: mov %ecx,0x8(%ebp)
 PC (0x00489f71) ok
 source "%ecx" ok
 destination "0x8(%ebp)" (0x0280000d) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: nux
StacktraceTop:
 ?? () from /lib/i386-linux-gnu/libc.so.6
 calloc () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_malloc0 () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_object_new_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: compiz crashed with SIGSEGV in calloc()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Daniel Clem (clem11388) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 _int_malloc (av=0x593400, bytes=384) at malloc.c:4439
 __libc_calloc (n=1, elem_size=384) at malloc.c:4065
 standard_calloc (n_blocks=1, n_bytes=384) at /build/buildd/glib2.0-2.30.0/./glib/gmem.c:107
 g_malloc0 (n_bytes=384) at /build/buildd/glib2.0-2.30.0/./glib/gmem.c:196
 g_object_new_valist (object_type=145335416, first_property_name=0x52da2b3 "data", var_args=0xbfa44b08 "") at /build/buildd/glib2.0-2.30.0/./gobject/gobject.c:1573

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 nux (Ubuntu):
importance: Undecided → Medium
summary: - compiz crashed with SIGSEGV in calloc()
+ compiz crashed with SIGSEGV in _int_malloc()
tags: removed: need-i386-retrace
Changed in nux (Ubuntu):
importance: Medium → Critical
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in nux (Ubuntu):
status: New → Confirmed
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

This bug appears to be the same heap corruption as bug 931201. So I will mark it as a duplicate unless proven otherwise.

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.