compiz crashed with SIGSEGV on shutdown

Bug #931283 reported by Daniel van Vugt on 2012-02-13
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Compiz Core
High
Alan Griffiths
compiz (Ubuntu)
Undecided
Unassigned

Bug Description

Running the latest lp:compiz-core (revision 2996) I get this crash on shutdown. I shut down compiz by pressing ^C

==21634== Invalid read of size 8
==21634== at 0x4E884D2: CompWindow::~CompWindow() (scoped_ptr.hpp:97)
==21634== by 0x4E88A18: CompWindow::~CompWindow() (window.cpp:6556)
==21634== by 0x4E6BCDA: PrivateScreen::~PrivateScreen() (screen.cpp:5016)
==21634== by 0x4E6BF68: PrivateScreen::~PrivateScreen() (screen.cpp:5054)
==21634== by 0x4E63383: CompScreenImpl::~CompScreenImpl() (checked_delete.hpp:34)
==21634== by 0x4E634B8: CompScreenImpl::~CompScreenImpl() (screen.cpp:4907)
==21634== by 0x402CC2: CompManager::fini() (main.cpp:214)
==21634== by 0x4029A5: main (main.cpp:239)
==21634== Address 0x98 is not stack'd, malloc'd or (recently) free'd
==21634==
==21634==
==21634== Process terminating with default action of signal 11 (SIGSEGV)
==21634== Access not within mapped region at address 0x98
==21634== at 0x4E884D2: CompWindow::~CompWindow() (scoped_ptr.hpp:97)
==21634== by 0x4E88A18: CompWindow::~CompWindow() (window.cpp:6556)
==21634== by 0x4E6BCDA: PrivateScreen::~PrivateScreen() (screen.cpp:5016)
==21634== by 0x4E6BF68: PrivateScreen::~PrivateScreen() (screen.cpp:5054)
==21634== by 0x4E63383: CompScreenImpl::~CompScreenImpl() (checked_delete.hpp:34)
==21634== by 0x4E634B8: CompScreenImpl::~CompScreenImpl() (screen.cpp:4907)
==21634== by 0x402CC2: CompManager::fini() (main.cpp:214)
==21634== by 0x4029A5: main (main.cpp:239)
==21634== If you believe this happened as a result of a stack
==21634== overflow in your program's main thread (unlikely but
==21634== possible), you can try to increase the size of the
==21634== main thread stack using the --main-stacksize= flag.
==21634== The main thread stack size used in this run was 8388608.
==21634==

Related branches

Daniel van Vugt (vanvugt) wrote :

Attached valgrind log.

Daniel van Vugt (vanvugt) wrote :

Assigning to Alan. The only scoped_ptr I can see is related to his recent screen changes.

Changed in compiz-core:
assignee: nobody → Alan Griffiths (alan-griffiths)
tags: added: compiz-0.9.7.0-beta1
tags: added: 0.9.7.0-beta1
removed: compiz-0.9.7.0-beta1
Alan Griffiths (alan-griffiths) wrote :

Yes, mine. :(

(Although the scoped_ptr is an innocent bystander.)

Tim Penhey (thumper) on 2012-02-13
Changed in compiz-core:
status: New → Fix Committed
Changed in compiz-core:
status: Fix Committed → Fix Released
Daniel van Vugt (vanvugt) wrote :

This bug was fixed in the package compiz - 1:0.9.7.0+bzr3035-0ubuntu1

---------------
compiz (1:0.9.7.0+bzr3035-0ubuntu1) precise; urgency=low

  [ Łukasz 'sil2100' Zemczak ]
  * New upstream snapshot:
    - Fix gtk-window-decorator crash upon demaximizing a window (LP: #930071)
    - Fix core keybindings (LP: #930412)
    - Fixes compiz crash with SIGSEGV on shutdown (LP: #931283)
    - Plugins can't tell the difference between a key-tap and modifier
      key-release (LP: #925293)
    - compiz-core r3001 (and 3002) ftbfs (LP: #933226)
    - Semi-maximized windows have no shadow or frame (LP: #924736)
    - Untranslated strings in gtk-window-decorator (LP: #780505)
    - Initialize the _NET_WM_STATE_FOCUSED (LP: #932087)
    - [regression] Customized shortcuts don't work (LP: #931927)
    - Window stacking problem (LP: #936675)
    - Quickly demaximized windows can receive maximized window decorations if
      they were initially maximized (LP: #936778)
    - Maximized windows do not get shadows at all (LP: #936774)
    - [regression] Launcher, top panel and keyboard un-responsive after using
      any Super-x shortcut (LP: #934058)
    - No draggable border if mutter isn't installed (LP: #936781)
    - Fix compiz crash with SIGSEGV in XDefineCursor() (LP: #936487)
    - Fixes memory leak at DecorWindow::updateSwitcher() (LP: #940115)
    - Unresolved symbols in plugins cause compiz to exit (LP: #938478)
    - Fix compiz spending about 51% of its CPU time in CompRegion
      construction/destruction (LP: #940139)
    - Fix Conditional jump or move depends on uninitialised value(s) in
      decor_match_pixmap (LP: #940066)
    - Fix 'show desktop' behaviour (LP: #871801)
    - Tweak algorithm used to cast shadows on maximized windows (LP: #936784)
    - "Svg" and "Png" should be "SVG and "PNG" (LP: #942890)
    - Fix invalid memory usage after free() in DecorWindow (LP: #943116)
    - Fix alt + F10 (LP: #943223)
  * Removed cherry-picked patches
  * debian/patches/fix_944631.patch:
    - Always replay the keyboard if something was grabbed and didn't trigger
      an action and don't trigger actions which aren't added accidentally
      (LP: #943612) (LP: #944631)
  * debian/patches/fix_923683.patch:
    - Backports a patch which prevents the shift race condition

  [ Didier Roche ]
  * debian/patches/fix_alt_pressing.patch:
    - Patch from ddv to fix all the regressions with the alt key fix and other
      (LP: #943851, #945373)
    - Fix Quicklist are not showing if right-clicking a launcher icon in Expo
      mode if triggered by Super + S (LP: #944979)
  * debian/patches/fix_806255.patch:
    - Unity/compiz intercepts keystrokes from grabbed windows (LP: #806255)
  * debian/patches/fix_943194.patch:
    - second part for the alt key fix (LP: #943194)
  * debian/patches/additional_alt_tapping_fix.patch:
    - again another alt tapping related fix for some regressions from the
      previous branch. Taken from "tapping-panacea" upstream branch.
 -- Didier Roche <email address hidden> Mon, 12 Mar 2012 10:22:10 +0100

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

Other bug subscribers

Bug attachments