Backport upstream fix for memleak

The commit is in the stable serie
https://git.gnome.org/browse/glib/commit/?h=glib-2-46&id=e98e1eff83c742c73a148dd7b75c00d77e0cee40

Iain said he could have a look, assigning to him, thanks!

I uploaded it, sorry for the delay!

It would be good if you could update the bug with the information from <https://wiki.ubuntu.com/StableReleaseUpdates#Procedure>, otherwise the SRU team might delay accepting the upload (hopefully not).

Thanks fellas!

Iain,

Was the SRU comment directed at me or Sebastien? I would be happy to update what I can later this evening, but some of the information requested there seems like it would better come from someone more familiar with the glib code base (potential regressions, etc).

On Tue, Mar 01, 2016 at 04:25:02PM -0000, Trent Nelson wrote:
> Thanks fellas!
>
> Iain,
>
> Was the SRU comment directed at me or Sebastien? I would be happy to
> update what I can later this evening, but some of the information
> requested there seems like it would better come from someone more
> familiar with the glib code base (potential regressions, etc).

It was you. I think the mainly interesting one is a clear list of steps
for reproducing the bug, so we can be sure that it is fixed. The
description is already decent, but if it were a step by step list it
would be even easier. :)

--
Iain Lane [ <email address hidden> ]
Debian Developer [ <email address hidden> ]
Ubuntu Developer [ <email address hidden> ]

Sorry, I spaced this. Description updated. :)

Hello Trent, or anyone else affected,

Accepted glib2.0 into wily-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/glib2.0/2.46.2-1ubuntu2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

I finally got around to enabling the package from proposed. I'll report back in a few days with results.

Hey Brian,

I was going to let this run longer, but I think we're safe. I've observed RSS of both xfce4-power-manager and NetworkManager grow by over 1.5MB from usage at start up and have now dropped back to more than 1MB below usage at start up. These observations were made with swap disabled, so they should be accurate. Without the patch, both would be ~50MB over start up usage by now.

This bug was fixed in the package glib2.0 - 2.46.2-1ubuntu2

---------------
glib2.0 (2.46.2-1ubuntu2) wily; urgency=medium

  * d/p/0001-GDBusProxy-Fix-a-memory-leak-during-initialization.patch:
    Cherry-pick upstream patch to fix a memleak in GDBusProxy (LP: #1545308)

 -- Iain Lane <email address hidden> Tue, 01 Mar 2016 13:05:30 +0000

The verification of the Stable Release Update for glib2.0 has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.