touch-packages team mailing list archive

[Launchpad Bug Tracker <1418910@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package mir - 0.13.1+15.10.20150520-0ubuntu1

---------------
mir (0.13.1+15.10.20150520-0ubuntu1) wily; urgency=medium

  [ Cemil Azizoglu ]
  * New upstream release 0.13.1 (https://launchpad.net/mir/+milestone/0.13.1)
    - ABI summary: No ABI break. Servers and clients do not need rebuilding.
      . Mirclient ABI unchanged at 8
      . Mircommon ABI unchanged at 4
      . Mirplatform ABI unchanged at 7
      . Mirserver ABI unchanged at 31
    - Bug fixes:
      . Can't load app purchase UI without a U1 account (LP: #1450377)
      . Crash because uncaught exception in mir::events::add_touch (LP: #1437357)

 -- CI Train Bot <ci-train-bot@xxxxxxxxxxxxx>  Wed, 20 May 2015 21:20:15
+0000

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

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

Title:
  Nested display leaks its EGLContext

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Because the EGLContext is current when we call eglTerminate() the
  context isn't really freed at that point and we end up leaking the
  EGLContext (a "still reachable" leak). Since we don't destroy and
  recreate the NestedDisplay (at least not currently) it's just memory
  leaked at process exit. Still, it would be good to fix, if only to
  clean up the valgrind output a bit and ease detection of other leaks.

  A side note: The way the EGL resources are managed in NestedDisplay
  leaves a lot to be desired (and could lead to other leaks in case the
  display is reconfigured), but that's a problem for another bug/MP.

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