touch-packages team mailing list archive

[Daniel van Vugt <daniel.van.vugt@xxxxxxxxxxxxx>]

Just missed the branching of 0.8 by a few hours.

** Changed in: mir
    Milestone: 0.8.0 => 0.9.0

** Also affects: mir/0.8
   Importance: Undecided
       Status: New

** Changed in: mir/0.8
   Importance: Undecided => High

** Changed in: mir/0.8
       Status: New => Triaged

** Changed in: mir/0.8
    Milestone: None => 0.8.0

** Also affects: mir (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: mir (Ubuntu)
   Importance: Undecided => High

** Changed in: mir (Ubuntu)
       Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1362841

Title:
  Some mali drivers crash after repeatedly creating/destroying the mir
  compositor threads

Status in Mir:
  Fix Committed
Status in Mir 0.8 series:
  Triaged
Status in “mir” package in Ubuntu:
  Triaged

Bug description:
  Some mali drivers crash after repeatedly creating/destroying the mir
  compositor threads.

  It's possible calling eglMakeCurrent on a new compositor thread
  multiple times exposes such a bug.

  Recycling the mir compositor threads seems to be a viable workaround.

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