compiz team mailing list archive

[Timo Jyrinki <timo.jyrinki@xxxxxxxxxxxxx>]

** Description changed:

+ [Impact]
+ 
+ A crash after fix to bug #755842.
+ 
+ [Test case]
+ 
+ Use super+W rapidly a few times.
+ 
+ [Regression Potential]
+ 
+ Should be low, correct usage of the vector variable. Test wall plugin's
+ offset movement functionality in general.
+ 
  TESTCASE:
  
  ctest -D ExperimentalMemCheck
  (this option was only added on 20 June 2012)
  
  ORIGINAL DESCRIPTION:
  Running compiz 1:0.9.8+bzr3249-0ubuntu1 got a crash in movementWindowOnScreen after doing super+W a few times.
  
  valgrind says:
  
  ==3648== Invalid read of size 2
  ==3648==    at 0x806092A: compiz::wall::movementWindowOnScreen(CompRect const&, CompRegion const&) (rect.h:178)
  ==3648==    by 0x44BCEC7: ???
  ==3648==  Address 0x44bd026 is 14 bytes inside a block of size 20 free'd
  ==3648==    at 0x402ACFC: operator delete(void*) (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
  ==3648==    by 0x8060965: compiz::wall::movementWindowOnScreen(CompRect const&, CompRegion const&) (new_allocator.h:98)
  ==3648==    by 0x44BCEC7: ???
  
  The classic case of iterating a temporary vector that goes out of scope
  while iterating. Annoying.

-- 
You received this bug notification because you are a member of compiz
packagers, which is subscribed to compiz in Ubuntu.
https://bugs.launchpad.net/bugs/1015151

Title:
  [BNR] Compiz crash in movementWindowOnScreen (caused by fix 755842)

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1015151/+subscriptions