compiz crashed with SIGSEGV in CompPlugin::windowFiniPlugins() [plugin.cpp:370] from CompWindow::~CompWindow() from compiz::private_screen::WindowManager::removeDestroyed() from PrivateScreen::processEvents()

Bug #1039668 reported by Cavsfan
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Compiz
New
Undecided
Unassigned
compiz (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Just setting up CCSM and it abended sending this error msg. It was not listed above.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: compiz-core 1:0.9.8+bzr3249-0ubuntu4
ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2
Uname: Linux 3.5.0-11-generic x86_64
ApportVersion: 2.4-0ubuntu8
Architecture: amd64
CrashCounter: 1
Date: Tue Aug 21 14:10:20 2012
Disassembly: => 0x5d305b6c6163: Cannot access memory at address 0x5d305b6c6163
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120724.2)
ProcCmdline: compiz --replace
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x5d305b6c6163: Cannot access memory at address 0x5d305b6c6163
 PC (0x5d305b6c6163) not located in a known VMA region (needed executable region)!
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
 ?? ()
 CompPlugin::windowFiniPlugins(CompWindow*) () from /usr/lib/libcompiz_core.so.ABI-20120526
 CompWindow::~CompWindow() () from /usr/lib/libcompiz_core.so.ABI-20120526
 CompWindow::~CompWindow() () from /usr/lib/libcompiz_core.so.ABI-20120526
 compiz::private_screen::WindowManager::removeDestroyed() () from /usr/lib/libcompiz_core.so.ABI-20120526
Title: compiz crashed with SIGSEGV in CompPlugin::windowFiniPlugins()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Cavsfan (cavsfan) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 CompPlugin::windowFiniPlugins (w=0x2a3a4c0) at /build/buildd/compiz-0.9.8+bzr3249/src/plugin.cpp:370
 CompWindow::~CompWindow (this=0x2a3a4c0, __in_chrg=<optimized out>) at /build/buildd/compiz-0.9.8+bzr3249/src/window.cpp:6243
 CompWindow::~CompWindow (this=0x2a3a4c0, __in_chrg=<optimized out>) at /build/buildd/compiz-0.9.8+bzr3249/src/window.cpp:6246
 compiz::private_screen::WindowManager::removeDestroyed (this=0x175b160) at /build/buildd/compiz-0.9.8+bzr3249/src/screen.cpp:4646

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.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
tags: added: compiz-0.9
visibility: private → public
summary: - compiz crashed with SIGSEGV in CompPlugin::windowFiniPlugins()
+ compiz crashed with SIGSEGV in CompPlugin::windowFiniPlugins() from
+ CompWindow::~CompWindow() from
+ compiz::private_screen::WindowManager::removeDestroyed() from
+ PrivateScreen::processEvents()
summary: - compiz crashed with SIGSEGV in CompPlugin::windowFiniPlugins() from
- CompWindow::~CompWindow() from
+ compiz crashed with SIGSEGV in CompPlugin::windowFiniPlugins()
+ [plugin.cpp:370] from CompWindow::~CompWindow() from
compiz::private_screen::WindowManager::removeDestroyed() from
PrivateScreen::processEvents()
Changed in compiz:
milestone: none → 0.9.8.0
Changed in compiz:
milestone: 0.9.8.0 → 0.9.8.1
Changed in compiz:
milestone: 0.9.8.2 → 0.9.8.4
Changed in compiz:
milestone: 0.9.8.4 → 0.9.9.0
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in compiz (Ubuntu):
status: New → Confirmed
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 956515, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

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

Other bug subscribers

Remote bug watches

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