compiz crashed with SIGSEGV in CompRegion::operator==()

Bug #734779 reported by ArbitRabbit
18
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Compiz
Incomplete
Undecided
Unassigned
compiz (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: compiz

Possibly a duplicate of #733903, but just thought will report it as it has more info attached.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: compiz-core 1:0.9.4-0ubuntu4
Uname: Linux 2.6.37-020637-generic x86_64
Architecture: amd64
CheckboxSubmission: 8d81d8a2e14e8058b9f6187a60ba8e48
CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2
CrashCounter: 1
Date: Mon Mar 14 11:22:59 2011
ExecutablePath: /usr/bin/compiz
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x41fd37 <_ZNK10CompRegioneqERKS_+7>: mov (%rdi),%rax
 PC (0x0041fd37) ok
 source "(%rdi)" (0x00000098) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
 CompRegion::operator==(CompRegion const&) const ()
 CompositeScreen::handlePaintTimeout() () from /usr/lib/compiz/libcomposite.so
 CompTimeoutSource::callback() ()
 CompTimeoutSource::dispatch(sigc::slot_base*) ()
 Glib::Source::dispatch_vfunc(_GSource*, int (*)(void*), void*) () from /usr/lib/libglibmm-2.4.so.1
Title: compiz crashed with SIGSEGV in CompRegion::operator==()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
ArbitRabbit (arbitrabbit) wrote :
affects: compiz (Ubuntu) → unity (Ubuntu)
affects: unity → compiz
visibility: private → public
Revision history for this message
Didier Roche-Tolomelli (didrocks) wrote :

The bug is i compiz itself, let's wait for it to be retraced.

affects: unity (Ubuntu) → compiz (Ubuntu)
tags: added: compiz-0.9
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 handle (this=0x98, c=...) at /build/buildd/compiz-0.9.4/src/region.cpp:110
 CompRegion::operator== (this=0x98, c=...) at /build/buildd/compiz-0.9.4/src/region.cpp:123
 CompositeScreen::handlePaintTimeout (this=0x896120) at /build/buildd/compiz-0.9.4/plugins/composite/src/screen.cpp:835
 operator() (this=<value optimized out>) at /usr/include/boost/function/function_template.hpp:1013
 CompTimeoutSource::callback (this=<value optimized out>) at /build/buildd/compiz-0.9.4/src/timer.cpp:151

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 compiz (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Alex Launi (alexlauni) wrote :

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
Changed in compiz:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in compiz (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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