@ddstreet

After analyzing code.

I don't think this fix is possible without any big changes for trusty.

and glib2.0 affects many pkgs it seems.

it is quite dangerous to fix this with large commits.

so lets focus on pacemaker instead of glib2.0

how about this ddstreet?

Thanks

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
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:
  Confirmed

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/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to