Ubuntu
compiz package

unity-window-decorator crashed with SIGSEGV in g_slice_alloc()

Bug #733417 reported by moises fernades de sousa on 2011-03-11

108

This bug affects 18 people

Affects		Status	Importance	Assigned to	Milestone
	compiz (Ubuntu)	Won't Fix	Medium	Unassigned

Bug Description

Binary package hint: compiz

flhou ao configurar os efeitos

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: compiz-gnome 1:0.9.4-0ubuntu4
ProcVersionSignature: Ubuntu 2.6.38-6.34-generic 2.6.38-rc7
Uname: Linux 2.6.38-6-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
CrashCounter: 1
Date: Fri Mar 11 11:52:44 2011
ExecutablePath: /usr/bin/unity-window-decorator
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110302)
ProcCmdline: /usr/bin/unity-window-decorator
ProcEnviron:
LANGUAGE=pt_BR:en
LANG=pt_BR.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f7d1dd52126 <g_slice_alloc+294>: mov (%rbx),%rdx
PC (0x7f7d1dd52126) ok
source "(%rbx)" (0xffffffff) not located in a known VMA region (needed readable region)!
destination "%rdx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
g_slice_alloc () from /lib/libglib-2.0.so.0
g_slice_alloc0 () from /lib/libglib-2.0.so.0
g_type_create_instance () from /usr/lib/libgobject-2.0.so.0
?? () from /usr/lib/libgobject-2.0.so.0
g_object_newv () from /usr/lib/libgobject-2.0.so.0
Title: unity-window-decorator crashed with SIGSEGV in g_slice_alloc()
UpgradeStatus: Upgraded to natty on 2011-03-09 (1 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

moises fernades de sousa (moises-cirilo) wrote on 2011-03-11:

Dependencies.txt Edit (5.0 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (1.1 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (36.7 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (799 bytes, text/plain; charset="utf-8")
Registers.txt Edit (680 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (1.6 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (2.5 KiB, text/plain; charset="utf-8")
XsessionErrors.txt Edit (1.6 KiB, text/plain; charset="utf-8")

visibility:

private → public

Revision history for this message

Apport retracing service (apport) wrote on 2011-03-11:

StacktraceTop:
magazine_chain_pop_head (mem_size=296) at /build/buildd/glib2.0-2.28.2/./glib/gslice.c:492
thread_memory_magazine1_alloc (mem_size=296) at /build/buildd/glib2.0-2.28.2/./glib/gslice.c:795
g_slice_alloc (mem_size=296) at /build/buildd/glib2.0-2.28.2/./glib/gslice.c:833
g_slice_alloc0 (mem_size=296) at /build/buildd/glib2.0-2.28.2/./glib/gslice.c:854
g_type_create_instance (type=6918784) at /build/buildd/glib2.0-2.28.2/./gobject/gtype.c:1869

Revision history for this message

Apport retracing service (apport) wrote on 2011-03-11: Stacktrace.txt

Stacktrace.txt Edit (11.7 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2011-03-11: ThreadStacktrace.txt

ThreadStacktrace.txt Edit (13.9 KiB, text/plain)

Changed in compiz (Ubuntu):
importance:	Undecided → Medium
tags:	removed: need-amd64-retrace

Ubuntu Foundations Team Bug Bot (crichton) on 2011-03-11

tags:

added: compiz-0.9

Revision history for this message

Alex Launi (alexlauni) wrote on 2011-08-19:

This bug has been sitting for quite some time (sorry about that). Do you continue to have this crash?

Changed in compiz (Ubuntu):
status:	New → Incomplete

Revision history for this message

Jean-Baptiste Lallement (jibel) wrote on 2011-10-04:

moving to confirmed due to recent duplicates

Changed in compiz (Ubuntu):
status:	Incomplete → Confirmed

Revision history for this message

Mark Wilkinson (mhw) wrote on 2011-10-25:

I've just filed bug #881670 and it has been marked as a duplicate of this one. I'm not sure it is, but that bug is reliably reproducible for me so should be easier to debug. Here's my description:

It's fairly common practice to use the setting 'set lines=999' in ~/.gvimrc to maximise the height of the gvim window to the - try Googling 'gvim lines=999' for examples. This setting will crash unity-window-decorator and gtk-window-decorator pretty reliably: starting and then quitting gvim two or three times will crash the window decorator for me.

Steps to reproduce:

Create a ~/.gvimrc file containing the text 'set lines=999'
From the command line, run 'gvim'
If the decorator is still running, quit gvim and repeat.

Revision history for this message

MC Return (mc-return) wrote on 2012-03-29:

Why not use Emerald as default to accomplish Unity/Compiz in the first place:

https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/968112

Revision history for this message

Will Cooke (willcooke) wrote on 2015-09-16:

As part of the big bug clear up for 16.04 LTS I am marking this bug as Wont Fix.
These types of crasher are better handled by errors.ubutnu.com which can collate similar crash reports to help us identify persitent bugs rather than one-off crashes.
Sorry we are not able to help with this specific issue. If you are still experiencing this crash, please re-open the bug and add the tag "desktop-bugscrub-reopened". See https://wiki.ubuntu.com/BigDesktopBugScrub for more information.

Changed in compiz (Ubuntu):
status:	Confirmed → Won't Fix
tags:	added: desktop-bugscrub-autoclosed

Report a bug

This report contains Public information

Everyone can see this information.

Duplicates of this bug

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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

Ubuntucompiz package

unity-window-decorator crashed with SIGSEGV in g_slice_alloc()

Bug Description

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
compiz package