Various issues in GPU code

Bug #1308412 reported by Chris Coulson on 2014-04-16
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Oxide
Undecided
Unassigned
oxide-qt (Ubuntu)
Undecided
Unassigned

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

Changed in oxide:
status: New → Fix Released
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package oxide-qt - 1.0.2-0ubuntu2

---------------
oxide-qt (1.0.2-0ubuntu2) utopic; urgency=medium

  * Update to v1.0.2
    - Bump Chromium to 36.0.1985.49
    - Add experimental support for the Google Talk PPAPI plugin, to support
      Google Hangouts. This is hidden behind an environment variable that
      defaults to off (LP: #1308397)
    - Fix crash in oxide::GetFormFactorHint() on Unity 8 desktop preview
      (LP: #1308398)
    - Fix various issues in GPU related code, including a crash (LP: #1308412)
    - Set no_javascript_access in ContentBrowserClient::CanCreateWindow()
      to fix random window opening failures (LP: #1307735)
    - Add fullscreen API to WebView (LP: #1308947)
    - Set a wait cursor when loading
    - Add geolocation support
    - Add a WebView.geolocationPermissionRequested API
    - Allow unhandled key events to bubble up from the WebView (LP: #1313727)
    - Don't generate keypress events with unmodified text for control
      characters. This makes Oxide behave more like Chrome
    - Add WebView.loadHtml() (LP: #1320848)
    - Ensure we update the visibility in a renderer when a WebView is created
      initially hidden and then made visible before any content is loaded
      (LP: #1322622)
    - Build fixes for Qt 5.3
    - Display controls in media player (LP: #1326852)
  * Refresh debian/patches/gross-hack-for-dual-ffmpeg-build.patch
  * Don't build with ENABLE_OXIDEQMLSCENE now, as that's the default
    - update debian/rules
  * Update build dependencies - we now depend on ninja
 -- Chris Coulson <email address hidden> Wed, 16 Apr 2014 09:54:56 +0100

Changed in oxide-qt (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