ubuntu-webapps-bugs team mailing list archive

[Chris Coulson <chris.coulson@xxxxxxxxxxxxx>]

** Changed in: oxide/1.4
       Status: Fix Committed => Fix Released

** Changed in: oxide/1.3
       Status: Triaged => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
WebApps bug tracking, which is subscribed to Oxide.
https://bugs.launchpad.net/bugs/1402382

Title:
  Possible leak due to thread safety issue

Status in Oxide Webview:
  Fix Released
Status in Oxide 1.3 series:
  Won't Fix
Status in Oxide 1.4 series:
  Fix Released

Bug description:
  CompositorFrameHandle isn't thread-safe and is intended to be used on
  the UI thread (although it's also used on the QML render thread when
  the UI thread is paused). As a consequence it doesn't use a thread-
  safe reference count.

  When calling Compositor::DidSwapCompositorFrame(), we check that the
  returned CompositorFrameHandles don't have a reference outside of the
  compositor, before handing them off to the compositor thread where
  they are deleted. However, even when there are no references held
  outside of the compositor, there is a race when the UI and compositor
  threads release their reference that means we may leak the object.

  This is fixed on trunk by http://bazaar.launchpad.net/~oxide-
  developers/oxide/oxide.trunk/revision/892

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