Seyeong,

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

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-
time.patch

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 STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1750741

Title:
  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:
  New

Bug description:
  [Impact]

  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]
  said

  this is affected to Trusty

  [Test Case]

  https://pastebin.ubuntu.com/p/fqK6Cx3SKK/
  you can check memory leak with this script

  [Regression]
  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 
years.

  [Others]

  original commit

  
https://gitlab.gnome.org/GNOME/glib/commit/db641e32920ee8b553ab6f2d318aafa156e4390c

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1750741/+subscriptions

-- 
Mailing list: https://launchpad.net/~sts-sponsors
Post to     : sts-sponsors@lists.launchpad.net
Unsubscribe : https://launchpad.net/~sts-sponsors
More help   : https://help.launchpad.net/ListHelp

Reply via email to