ubuntu-webapps-bugs team mailing list archive

[Chris Coulson <chris.coulson@xxxxxxxxxxxxx>]

Public bug reported:

There are various issues in the code that communicates with Chromium's
GPU thread. At least one of these causes an application crash under some
conditions

- We're accessing members of the GpuChildThread singleton off the GPU thread in order to dispatch tasks to it. GpuChildThread is not thread safe, so we should store the singleton pointer in TLS to make it unavailable to other threads and provide a function to access the thread-safe MessageLoopProxy to dispatch tasks to the GPU thread
- We use the wrong MailboxManager instance to consume textures from Chromium's compositor
- We don't ensure we have a current GL context when deleting textures, which results in us hitting a runtime abort inside Chromium

** Affects: oxide
     Importance: Undecided
         Status: Fix Released

** Affects: oxide-qt (Ubuntu)
     Importance: Undecided
         Status: New

** Changed in: oxide
       Status: New => Fix Released

** Also affects: oxide-qt (Ubuntu)
   Importance: Undecided
       Status: New

-- 
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/1308412

Title:
  Various issues in GPU code

Status in Oxide Webview:
  Fix Released
Status in “oxide-qt” package in Ubuntu:
  New

Bug description:
  There are various issues in the code that communicates with Chromium's
  GPU thread. At least one of these causes an application crash under
  some conditions

  - We're accessing members of the GpuChildThread singleton off the GPU thread in order to dispatch tasks to it. GpuChildThread is not thread safe, so we should store the singleton pointer in TLS to make it unavailable to other threads and provide a function to access the thread-safe MessageLoopProxy to dispatch tasks to the GPU thread
  - We use the wrong MailboxManager instance to consume textures from Chromium's compositor
  - We don't ensure we have a current GL context when deleting textures, which results in us hitting a runtime abort inside Chromium

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