touch-packages team mailing list archive

Thread
Date

[Bug 1418910] Re: Nested display leaks its EGLContext

To: touch-packages@xxxxxxxxxxxxxxxxxxx
From: Alan Griffiths <1418910@xxxxxxxxxxxxxxxxxx>
Date: Tue, 19 May 2015 13:51:28 -0000
Reply-to: Bug 1418910 <1418910@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

** Changed in: mir
       Status: Fix Committed => 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:
  Triaged

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