Ubuntu
nux package

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

Bug #881442 reported by Jonathan Yip
20
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

Crash when idling.

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.4-ck1-ck-bfq x86_64
ApportVersion: 1.23-0ubuntu3
Architecture: amd64
Date: Tue Oct 25 14:32:51 2011
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcCmdline: compiz
SegvAnalysis:
 Segfault happened at: 0x7f454cff2420 <_ZNK3nux12WindowThread19IsInsideLayoutCycleEv>: movzbl 0x250(%rdi),%eax
 PC (0x7f454cff2420) ok
 source "0x250(%rdi)" (0x00000250) 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::HLayout::HLayoutManagement(int, int) () from /usr/lib/libnux-1.0.so.0
 nux::HLayout::ComputeLayout2() () from /usr/lib/libnux-1.0.so.0
 nux::View::ComputeChildLayout() () from /usr/lib/libnux-1.0.so.0
Title: compiz crashed with SIGSEGV in nux::WindowThread::IsInsideLayoutCycle()
UpgradeStatus: Upgraded to oneiric on 2011-10-14 (10 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare src wireshark

Revision history for this message
Jonathan Yip (helkaluin) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 IsDerivedFromType (Type=<optimized out>, this=<optimized out>) at ../NuxCore/ObjectType.h:79
 nux::WindowThread::ComputeElementLayout (this=0x175fe10, area=0x0, recurse_to_top_level_layout=176) at ./WindowThread.cpp:803
 ?? ()

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
tags: removed: need-amd64-retrace
Didier Roche-Tolomelli (didrocks)
Changed in nux (Ubuntu):
importance: Medium → Critical
Omer Akram (om26er)
visibility: private → public
Revision history for this message
Bilal Akhtar (bilalakhtar) wrote :

What do you mean by idling? Was the system in suspend, hibernate, or was the screen locked, or just nothing?

Changed in nux:
status: New → Incomplete
Changed in nux (Ubuntu):
status: New → Incomplete
Changed in unity:
status: New → Incomplete
Revision history for this message
Jonathan Yip (helkaluin) wrote :

I really can't remember if I had been resuming from suspend. I do remember it's not strictly idling as in I-have-been-staring-at-my-computer-for-an-hour: I was reading a maximised window of Evolution on Workspace 3, there was no scrolling, and there was no user input for a while.

Revision history for this message
Dmitry Shachnev (mitya57) wrote :

No more awaiting feedback.

Changed in nux:
status: Incomplete → New
Changed in unity:
status: Incomplete → New
Changed in nux (Ubuntu):
status: Incomplete → New
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
Dmitry Shachnev (mitya57) wrote :

BTW, isn't it a duplicate of bug 864686?

Revision history for this message
Bilal Akhtar (bilalakhtar) wrote :

The stacktrace contents of bug #864686 are slightly different from those of this one, but I can safely assume that they both refer to the same issue.

Is this fixed now? That bug was fixed earlier this month.

Revision history for this message
Bilal Akhtar (bilalakhtar) wrote :

Okay, so a closer examination of the stacktrace reveals that it IS the same issue, the reason why apport didn't mark it so was because this bug was filed in December and that one in October, and Nux/Unity had changed quite a bit in that time frame, hence the difference in stack traces.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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