+     - d/p/0001-GDBusProxy-Fix-a-memory-leak-during-

this fixes a memory leak, but in later code than the Trusty glib2.0 code

+     - d/p/0001-tests-gdatetime-Use-a-real-rather-than-invented-

this fixes an autopkgtest regression, that's unrelated to this memleak
bug - it's ok to include in the same upload, but it needs its own lp
bug.  This is also needed in xenial glib2.0.

+     - d/p/0001-gio-Add-names-to-idles-and-timeouts.patch
+     - d/p/0002-gio-belatedly-port-gdbus-from-GSimpleAsyncResult-to-.patch

these patches are huge backports, that update the glib2.0 code to use a
different function that appears to *introduce* the memleak that your
first patch "fixes".  Are you sure there is actually a memleak in the
Trusty glib2.0 code?  If so, it does not seem to be the one that your
first patch fixes.  In any case, this huge backport is not acceptable as
a SRU for only a memleak.

You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.

  Memory leak in g_dbus_proxy_new_for_bus_sync()

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Trusty:

Bug description:

  This issue is found while debugging pacemaker lrmd memory leak

  glib2.0 gio function g_dbus_proxy_new_for_bus_sync has leak as [1]

  this is affected to Trusty

  [Test Case]
  you can check memory leak with this script

  This patch is affected to library pkg. so related daemon should be restarted 
after patching. patch itself is very simple and old. it seems verified for few 


  original commit

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to