Ubuntu
nux package

compiz crashed with SIGSEGV in __libc_free()

Bug #740757 reported by Martin Pitt on 2011-03-23

This bug affects 2 people

	Status	Importance	Assigned to
Nux	Fix Released	Medium	Jay Taoko
Unity	Fix Released	Medium	Jason Smith
nux (Ubuntu)	Incomplete	Medium	Unassigned
unity (Ubuntu)	Fix Released	Undecided	Unassigned

Bug Description

After today's upgrade and a reboot, compiz immediately crashed twice once I started opening windows, i. e. a few seconds after logging in.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: libnux-0.9-0 0.9.34-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-7.38-generic 2.6.38
Uname: Linux 2.6.38-7-generic x86_64
Architecture: amd64
Date: Wed Mar 23 08:00:13 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110302)
ProcCmdline: compiz
ProcEnviron:
LANGUAGE=de:en
PATH=(custom, user)
LANG=de_DE.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f1549c4e8c3 <__libc_free+83>: lock cmpxchg %esi,(%rbx)
PC (0x7f1549c4e8c3) ok
source "%esi" ok
destination "(%rbx)" (0x7f1568000012) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: nux
StacktraceTop:
__libc_free (mem=0x7f1528209470) at malloc.c:3736
?? () from /lib/x86_64-linux-gnu/libdrm_intel.so.1
?? () from /lib/x86_64-linux-gnu/libdrm_intel.so.1
intel_region_release () from /usr/lib/dri/i965_dri.so
intel_miptree_release () from /usr/lib/dri/i965_dri.so
Title: compiz crashed with SIGSEGV in __libc_free()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin dialout lpadmin sambashare

Tags:

Revision history for this message

Martin Pitt (pitti) wrote on 2011-03-23:

Dependencies.txt Edit (1.8 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (1.1 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (83.0 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (787 bytes, text/plain; charset="utf-8")
Registers.txt Edit (760 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (8.8 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (13.0 KiB, text/plain; charset="utf-8")
XsessionErrors.txt Edit (1.5 KiB, text/plain; charset="utf-8")

Revision history for this message

Martin Pitt (pitti) wrote on 2011-03-23:

I just noticed the (probably) duplicate bug 739434, where Brian said he used Alt+Arrow keys quickly. My session launch script does the same with a lot of wmctrl calls.

Revision history for this message

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

StacktraceTop:
__libc_free (mem=0x7f1528209470) at malloc.c:3736
?? () from /lib/x86_64-linux-gnu/libdrm_intel.so.1
?? () from /lib/x86_64-linux-gnu/libdrm_intel.so.1
intel_region_release (region_handle=0x2dc7aa8) at intel_regions.c:294
intel_miptree_release (intel=<value optimized out>, mt=0x2785668) at intel_mipmap_tree.c:204

Revision history for this message

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

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

Revision history for this message

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

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

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

Martin Pitt (pitti) on 2011-03-23

visibility:

private → public

Alex Launi (alexlauni) on 2011-03-28

Changed in nux (Ubuntu):
status:	New → Confirmed
Changed in unity:
status:	New → Confirmed
Changed in nux:
status:	New → Confirmed
assignee:	nobody → Jay Taoko (jaytaoko)
importance:	Undecided → Medium
Changed in unity:
importance:	Undecided → Medium

Revision history for this message

Jay Taoko (jaytaoko) wrote on 2011-03-28:

I cannot reproduce it on my intel system with nux 0.9.36. Try to reproduce with the latest Unity release.
If this bug still happens with a stack that traces back to the driver code, then it should be reported as a driver bug.

Changed in nux:
status:	Confirmed → Incomplete
Changed in unity:
status:	Confirmed → Incomplete
Changed in nux (Ubuntu):
status:	Confirmed → Incomplete
status:	Incomplete → Confirmed

Didier Roche-Tolomelli (didrocks) on 2011-03-29

Changed in unity:
status:	Incomplete → Confirmed
Changed in nux:
status:	Incomplete → Confirmed

Revision history for this message

Didier Roche-Tolomelli (didrocks) wrote on 2011-03-29:

@Jay: can you think to revert all tasks? (you didn't revert the nux downstream one) when reverting to a previous state? You fooled my script ;) Setting back to Incomplete :)

Changed in nux:
status:	Confirmed → Incomplete
Changed in unity:
status:	Confirmed → Incomplete
Changed in nux (Ubuntu):
status:	Confirmed → Incomplete

Jason Smith (jassmith) on 2011-04-02

Changed in unity:
assignee:	nobody → Jason Smith (jassmith)
status:	Incomplete → Fix Released

Didier Roche-Tolomelli (didrocks) on 2011-04-05

Changed in nux:
status:	Incomplete → Fix Released

Marco Trevisan (Treviño) (3v1n0) on 2014-07-25

Changed in unity (Ubuntu):
status:	New → Fix Released

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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

Ubuntunux package

compiz crashed with SIGSEGV in __libc_free()

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
nux package