Ubuntu
nux package

compiz crashed with SIGSEGV in nux::WindowThread::IsInsideLayoutCycle()

Bug #870933 reported by luis navarro on 2011-10-08

36

This bug affects 8 people

Affects		Status	Importance	Assigned to	Milestone
	Nux	Incomplete	Undecided	Unassigned
	Unity	Expired	Undecided	Unassigned
	nux (Ubuntu)	Expired	Undecided	Unassigned

Bug Description

compiz crashed when tried to change cursor

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: libnux-1.0-0 1.14.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
NonfreeKernelModules: fglrx
ApportVersion: 1.23-0ubuntu2
Architecture: i386
CrashCounter: 1
Date: Sat Oct 8 13:05:58 2011
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcCmdline: compiz
SegvAnalysis:
Segfault happened at: 0x1ab3da4 <_ZNK3nux12WindowThread19IsInsideLayoutCycleEv+4>: movzbl 0x130(%eax),%eax
PC (0x01ab3da4) ok
source "0x130(%eax)" (0x00000130) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nux
StacktraceTop:
nux::WindowThread::IsInsideLayoutCycle() const () from /usr/lib/libnux-1.0.so.0
nux::Area::ReconfigureParentLayout(nux::Area*) () from /usr/lib/libnux-1.0.so.0
nux::Area::SetGeometry(int, int, int, int) () from /usr/lib/libnux-1.0.so.0
nux::InputArea::InputArea(char const*, int) () from /usr/lib/libnux-1.0.so.0
nux::View::View(char const*, int) () from /usr/lib/libnux-1.0.so.0
Title: compiz crashed with SIGSEGV in nux::WindowThread::IsInsideLayoutCycle()
UpgradeStatus: Upgraded to oneiric on 2011-09-25 (13 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare sixad tape video

Tags:

Revision history for this message

luis navarro (bluis-714-l) wrote on 2011-10-08:

#1

Dependencies.txt Edit (1.5 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (1.4 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (141 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (44.1 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (813 bytes, text/plain; charset="utf-8")
Registers.txt Edit (504 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (4.3 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (6.3 KiB, text/plain; charset="utf-8")
XsessionErrors.txt Edit (2.4 KiB, text/plain; charset="utf-8")

Revision history for this message

Launchpad Janitor (janitor) wrote on 2011-10-17:

#2

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

Changed in nux (Ubuntu):
status:	New → Confirmed

Revision history for this message

tekstr1der (tekstr1der) wrote on 2011-10-17:

#3

compiz crashed when I restarted the unity shell with:

unity --replace

Didier Roche-Tolomelli (didrocks) on 2011-10-25

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

Revision history for this message

mthome (mthome) wrote on 2011-11-15:

#4

crashed after "unity --reset", which I tried after observing that compiz had been using 25-30% of a cpu for two days at idle

Revision history for this message

Alex Shulgin (alex-shulgin) wrote on 2011-12-01:

#5

> crashed after "unity --reset", which I tried after observing that compiz had been using 25-30% of a cpu for two days at idle

Same here.

I'm using indicator-multiload applet and on both Unity and Unity2d either compiz or unity-2d-panel process accumulate memory leaks and grow CPU consumption over time. With Unity2d it's as simple as killall unity-2d-panel, and you may have another two days w/o noticing.

Tried killall compiz now, and it crashed like this.

Revision history for this message

Dmitry Shachnev (mitya57) wrote on 2011-12-17:

#6

Very similar to bug 864686, probably a duplicate?

tags:

added: likely-dup

Revision history for this message

Omer Akram (om26er) wrote on 2012-07-24:

#7

Thanks for taking time to report this bug and helping to make ubuntu better. Its been a while since this bug was reported, there have been alot of changes in Unity since then. Can you please test with Ubuntu 12.04 with all updates installed and let us know if the issue is still there.

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

Revision history for this message

Launchpad Janitor (janitor) wrote on 2012-09-23:

#8

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

Changed in nux (Ubuntu):
status:	Incomplete → Expired

Revision history for this message

Launchpad Janitor (janitor) wrote on 2012-09-23:

#9

[Expired for Unity because there has been no activity for 60 days.]

Changed in unity:
status:	Incomplete → Expired

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

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