compiz crashed with SIGSEGV in memmove()

Bug #1040780 reported by Jonathan Reed
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
compiz (Ubuntu)
New
Medium
Unassigned

Bug Description

This was generated by apport, but Compiz is completely unstable and basically unusable in VMware (8.0.4, on a Precise host, Quantal guest, vmware tools not installed, VM has 2G of RAM). I see all sorts of display corruption, including missing titlebars on windows, lots of flicker when moving a window. The corruption/flicker is the worst in compositing situations (e.g. notify-osd, whatever the fast-user-switching-applet is called these days ("the power icon menu"), and the lens. The corruption gets worse and worse until Compiz finally crashes (as it did here). It's possibly relevant that it thinks my display (in the VM) is something like 3880 pixels wide (even the hosts's display is nowhere near that big).

My normal workaround would be to switch to Metacity, but since Unity is implemented entirely as a Compiz plugin now, metacity is basically useless, since I can't launch apps, etc.

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.5.1-0ubuntu1
Architecture: amd64
Date: Thu Aug 23 10:02:39 2012
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120724.2)
ProcCmdline: compiz
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f818371cfae: movaps %xmm1,-0x10(%rdi)
 PC (0x7f818371cfae) ok
 source "%xmm1" ok
 destination "-0x10(%rdi)" (0x11aa95870) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
 ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
 TfpTexture::enable(GLTexture::Filter) () from /usr/lib/compiz/libopengl.so
 GLWindow::glDrawTexture(GLTexture*, GLFragment::Attrib&, unsigned int) () from /usr/lib/compiz/libopengl.so
Title: compiz crashed with SIGSEGV in TfpTexture::enable()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Jonathan Reed (jdreed) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 memmove (__len=30724, __src=<optimized out>, __dest=<optimized out>) at /usr/include/x86_64-linux-gnu/bits/string3.h:58
 drisw_update_tex_buffer (drawable=<optimized out>, ctx=<optimized out>, res=<optimized out>) at drisw.c:272
 dri_set_tex_buffer2 (pDRICtx=<optimized out>, target=3553, format=8410, dPriv=<optimized out>) at dri_drawable.c:234
 GLWindow::glDrawTexture(GLTexture*, GLFragment::Attrib&, unsigned int) () from /tmp/tmpF0pZcu/usr/lib/compiz/libopengl.so
 ?? ()

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
summary: - compiz crashed with SIGSEGV in TfpTexture::enable()
+ compiz crashed with SIGSEGV in memmove()
tags: removed: need-amd64-retrace
tags: added: compiz-0.9
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 927168, 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.