compiz crashed with SIGSEGV in WallScreen::drawCairoTextureOnScreen()

Bug #740854 reported by Ries on 2011-03-23
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Unity
Won't Fix
Medium
Sam Spilsbury
compiz (Ubuntu)
Medium
Sam Spilsbury
unity (Ubuntu)
Medium
Sam Spilsbury

Bug Description

Binary package hint: unity

starting compiz

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: unity 3.6.6-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-7.38-generic 2.6.38
Uname: Linux 2.6.38-7-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Wed Mar 23 10:55:11 2011
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=en_DK:en
 LANG=en_DK.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f42e01c3e59 <_ZN10WallScreen24drawCairoTextureOnScreenEv+377>: mov (%rax),%rdi
 PC (0x7f42e01c3e59) ok
 source "(%rax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 WallScreen::drawCairoTextureOnScreen() () from /usr/lib/compiz/libwall.so
 WallScreen::glPaintOutput(GLScreenPaintAttrib const&, GLMatrix const&, CompRegion const&, CompOutput*, unsigned int) () from /usr/lib/compiz/libwall.so
 GLScreen::glPaintOutput(GLScreenPaintAttrib const&, GLMatrix const&, CompRegion const&, CompOutput*, unsigned int) () from /usr/lib/compiz/libopengl.so
 UnityScreen::glPaintOutput(GLScreenPaintAttrib const&, GLMatrix const&, CompRegion const&, CompOutput*, unsigned int) () from /usr/lib/compiz/libunityshell.so
 GLScreen::glPaintOutput(GLScreenPaintAttrib const&, GLMatrix const&, CompRegion const&, CompOutput*, unsigned int) () from /usr/lib/compiz/libopengl.so
Title: compiz crashed with SIGSEGV in WallScreen::drawCairoTextureOnScreen()
UpgradeStatus: Upgraded to natty on 2011-03-23 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Ries (riesvdam) wrote :

StacktraceTop:
 WallScreen::drawCairoTextureOnScreen (this=0x28c0c90) at /build/buildd/compiz-plugins-main-0.9.4git20110322/wall/src/wall.cpp:927
 WallScreen::glPaintOutput (this=0x28c0c90, attrib=..., matrix=..., region=..., output=0x264ef90, mask=15) at /build/buildd/compiz-plugins-main-0.9.4git20110322/wall/src/wall.cpp:1153
 __destroy<GLFragment::BodyOp*> (this=0x7f42e31d9192, __in_chrg=<value optimized out>) at /usr/include/c++/4.5/bits/stl_construct.h:98
 _Destroy<GLFragment::BodyOp*> (this=0x7f42e31d9192, __in_chrg=<value optimized out>) at /usr/include/c++/4.5/bits/stl_construct.h:122
 _Destroy<GLFragment::BodyOp*, GLFragment::BodyOp> (this=0x7f42e31d9192, __in_chrg=<value optimized out>) at /usr/include/c++/4.5/bits/stl_construct.h:148

Changed in unity (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
visibility: private → public
Alex Launi (alexlauni) on 2011-03-28
Changed in compiz (Ubuntu):
importance: Undecided → Medium
Changed in unity:
importance: Undecided → Medium
Changed in compiz (Ubuntu):
assignee: nobody → Sam "SmSpillaz" Spilsbury (smspillaz)
Changed in unity:
status: New → Confirmed
Changed in compiz (Ubuntu):
status: New → Confirmed
Changed in unity (Ubuntu):
status: New → Confirmed
Neil J. Patel (njpatel) wrote :

After, some investigation with Jason, it seems that the wall plugin pointer is invalid as it crashes on when the function accesses the first member variable. Hope that helps sam!

David Barth (dbarth) on 2011-04-06
Changed in unity:
milestone: none → 3.8.4
assignee: nobody → Sam "SmSpillaz" Spilsbury (smspillaz)
Sam Spilsbury (smspillaz) wrote :

Need some more info on how to reproduce this and / or a valgrind trace

Changed in unity:
status: Confirmed → Incomplete
Didier Roche (didrocks) on 2011-04-07
Changed in unity:
milestone: 3.8.4 → 3.8.6
Didier Roche (didrocks) on 2011-04-08
Changed in unity:
status: Incomplete → Confirmed
Didier Roche (didrocks) on 2011-04-11
Changed in unity:
milestone: 3.8.6 → 3.8.8
Didier Roche (didrocks) on 2011-04-14
Changed in unity:
milestone: 3.8.8 → 3.8.10
Sam Spilsbury (smspillaz) wrote :

The stack is trashed on this one, so marking incomplete until we can get a better stacktrace or instructions to reproduce.

Changed in unity:
status: Confirmed → Incomplete
Changed in compiz (Ubuntu):
status: Confirmed → Incomplete
Changed in unity (Ubuntu):
status: Confirmed → Incomplete
David Barth (dbarth) on 2011-04-18
Changed in unity:
milestone: 3.8.10 → 3.8.12
David Barth (dbarth) wrote :

@Sam: can you confirm that a static inspection of the code, as indicated on comment #5, doesn't give more hint at the cause of the issue. Otherwise, in the absence of a reproducible test case, and no duplicates, we could consider this bug invalid.

Changed in unity:
milestone: 3.8.12 → 3.8.14

It's not possible that WallScreen::get () will give you an invalid
pointer, the only screen variable available is global, it is not
touched by plugins and WallScreen::get () would crash on its own if it
was passed an invalid pointer rather than giving an invalid pointer
itself to a WallScreen *.

On Fri, Apr 22, 2011 at 8:04 PM, David Barth <email address hidden> wrote:
> @Sam: can you confirm that a static inspection of the code, as indicated
> on comment #5, doesn't give more hint at the cause of the issue.
> Otherwise, in the absence of a reproducible test case, and no
> duplicates, we could consider this bug invalid.
>
> ** Changed in: unity
>    Milestone: 3.8.12 => 3.8.14
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/740854
>
> Title:
>  compiz crashed with SIGSEGV in WallScreen::drawCairoTextureOnScreen()
>
> Status in Unity:
>  Incomplete
> Status in “compiz” package in Ubuntu:
>  Incomplete
> Status in “unity” package in Ubuntu:
>  Incomplete
>
> Bug description:
>  Binary package hint: unity
>
>  starting compiz
>
>  ProblemType: Crash
>  DistroRelease: Ubuntu 11.04
>  Package: unity 3.6.6-0ubuntu2
>  ProcVersionSignature: Ubuntu 2.6.38-7.38-generic 2.6.38
>  Uname: Linux 2.6.38-7-generic x86_64
>  NonfreeKernelModules: nvidia
>  Architecture: amd64
>  Date: Wed Mar 23 10:55:11 2011
>  ExecutablePath: /usr/bin/compiz
>  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
>  ProcCmdline: compiz
>  ProcEnviron:
>   LANGUAGE=en_DK:en
>   LANG=en_DK.UTF-8
>   SHELL=/bin/bash
>  SegvAnalysis:
>   Segfault happened at: 0x7f42e01c3e59 <_ZN10WallScreen24drawCairoTextureOnScreenEv+377>:      mov    (%rax),%rdi
>   PC (0x7f42e01c3e59) ok
>   source "(%rax)" (0x00000000) not located in a known VMA region (needed readable region)!
>   destination "%rdi" ok
>  SegvReason: reading NULL VMA
>  Signal: 11
>  SourcePackage: unity
>  StacktraceTop:
>   WallScreen::drawCairoTextureOnScreen() () from /usr/lib/compiz/libwall.so
>   WallScreen::glPaintOutput(GLScreenPaintAttrib const&, GLMatrix const&, CompRegion const&, CompOutput*, unsigned int) () from /usr/lib/compiz/libwall.so
>   GLScreen::glPaintOutput(GLScreenPaintAttrib const&, GLMatrix const&, CompRegion const&, CompOutput*, unsigned int) () from /usr/lib/compiz/libopengl.so
>   UnityScreen::glPaintOutput(GLScreenPaintAttrib const&, GLMatrix const&, CompRegion const&, CompOutput*, unsigned int) () from /usr/lib/compiz/libunityshell.so
>   GLScreen::glPaintOutput(GLScreenPaintAttrib const&, GLMatrix const&, CompRegion const&, CompOutput*, unsigned int) () from /usr/lib/compiz/libopengl.so
>  Title: compiz crashed with SIGSEGV in WallScreen::drawCairoTextureOnScreen()
>  UpgradeStatus: Upgraded to natty on 2011-03-23 (0 days ago)
>  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
>

--
Sam Spilsbury

Didier Roche (didrocks) on 2011-05-03
Changed in unity:
milestone: 3.8.14 → backlog
Charlie Kravetz (charlie-tca) wrote :

Please try to obtain a backtrace following the instructions at https://wiki.ubuntu.com/DebuggingCompiz#Advanced%20Debugging and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

It would also help greatly if you could tell us how to reproduce this crash. Attempts to reproduce it using the information given are not working.

Thank you for helping improve Ubuntu.

Launchpad Janitor (janitor) wrote :

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

Changed in unity (Ubuntu):
status: Incomplete → Expired
Omer Akram (om26er) on 2011-07-26
Changed in unity:
status: Incomplete → Invalid
Changed in compiz (Ubuntu):
status: Incomplete → Invalid
Ben Howard (utlemming) on 2011-09-01
Changed in unity:
status: Invalid → Incomplete
Changed in compiz (Ubuntu):
status: Invalid → Incomplete
Ben Howard (utlemming) wrote :

After updating to the lastest in the channel, this problem seems to have resolved itself for me.

Tim Penhey (thumper) on 2012-09-14
Changed in unity:
milestone: backlog → none
Tim Penhey (thumper) on 2012-09-14
tags: added: exbacklog
Changed in unity (Ubuntu):
status: Expired → Incomplete
assignee: nobody → Sam Spilsbury (smspillaz)
Will Cooke (willcooke) wrote :

As part of the big bug clear up for 16.04 LTS I am marking this bug as Wont Fix.
These types of crasher are better handled by errors.ubutnu.com which can collate similar crash reports to help us identify persitent bugs rather than one-off crashes.
Sorry we are not able to help with this specific issue. If you are still experiencing this crash, please re-open the bug and add the tag "desktop-bugscrub-reopened". See https://wiki.ubuntu.com/BigDesktopBugScrub for more information.

Changed in unity:
status: Incomplete → Won't Fix
Changed in unity (Ubuntu):
status: Incomplete → Won't Fix
tags: added: desktop-bugscrub-autoclosed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers