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

[Dmitry Shachnev]

Likely a duplicate of bug 864686 or bug 881442.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: libnux-1.0-0 1.16.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
Uname: Linux 3.0.0-14-generic i686
ApportVersion: 1.23-0ubuntu4
Architecture: i386
Date: Sat Dec 17 13:07:45 2011
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
ProcCmdline: compiz
SegvAnalysis:
 Segfault happened at: 0x16b4e94 <_ZNK3nux12WindowThread19IsInsideLayoutCycleEv+4>: movzbl 0x130(%eax),%eax
 PC (0x016b4e94) 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::ApplyMinWidth() () 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
Title: compiz crashed with SIGSEGV in nux::WindowThread::IsInsideLayoutCycle()
UpgradeStatus: Upgraded to oneiric on 2011-12-10 (6 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev nopasswdlogin plugdev sambashare tape video

[Apport retracing service (apport)]

StacktraceTop:
 nux::WindowThread::IsInsideLayoutCycle (this=0x0) at ./WindowThread.cpp:785
 IsComputingLayout (this=<optimized out>) at ./WindowThread.h:172
 nux::Area::ReconfigureParentLayout (this=0xa60a948, child=0x0) at ./Area.cpp:422
 nux::Area::ApplyMinWidth (this=0xa60a948) at ./Area.cpp:175
 nux::HLayout::HLayoutManagement (this=0xa6dfc08, width=1440, height=24) at ./HLayout.cpp:556

[Launchpad Janitor (janitor)]

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

[Omer Akram (om26er)]

Thanks for the bug report. Is that still an issue for you Ubuntu 12.04 with all updates applied? Can you please test that and let us know?

[Dmitry Shachnev (mitya57)]

No, I haven't got this bug since then.