Thanks Łukasz, I've tested the pacemaker packages in -proposed and they fixed the issue for me. The version I've tested is: 1.1.10+git20130802-1ubuntu2.5 .
The test was performed like this: I have a test-case that I ran against the version in trusty-updates (call it baseline); then I performed the packages' update to -proposed version and re-ran the test-case (call it proposed). I've observed a memory leak of 4.5MB during 1 hour in the baseline. After update it, I've observed a 64K memory increase in 1 hour, but 60K of it was "leaked" in the first 30 minutes. I don't believe this is a real memory leak, as explained in my previous comments. Valgrind didn't show anything, seems a normal application behavior. Thanks, Guilherme ** Tags removed: sts-sru-needed verification-needed verification-needed-trusty ** Tags added: verification-done verification-done-trusty -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1316970 Title: g_dbus memory leak in lrmd Status in pacemaker package in Ubuntu: Fix Released Status in pacemaker source package in Trusty: Fix Committed Bug description: [Impact] lrmd daemon with upstart resource has memory leak in Trusty affected to pacemaker 1.1.10. affected to glib2.0 2.40.2-0ubuntu1 >> for glib2.0 created new lp [1] Please note that patch for pacemaker is created myself. [Test Case] https://pastebin.ubuntu.com/p/fqK6Cx3SKK/ you can check memory leak with this script [Regression] Restarting daemon after upgrading this pkg will be needed. this patch adds free for non-freed dynamic allocated memory. so it solves memory leak. [Others] this patch is from my self with testing. Please review carefully if it is ok. [1] https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1750741 [Original Description] I'm running Pacemaker 1.1.10+git20130802-1ubuntu1 on Ubuntu Saucy (13.10) and have encountered a memory leak in lrmd. The details of the bug are covered here in this thread (http://oss.clusterlabs.org/pipermail/pacemaker/2014-May/021689.html) but to summarise, the Pacemaker developers believe the leak is caused by the g_dbus API, the use of which was removed in Pacemaker 1.11. I've also attached the Valgrind output from the run that exposed the issue. Given that this issue affects production stability (a periodic restart of Pacemaker is required), will a version of 1.11 be released for Trusty? (I'm happy to upgrade the OS to Trusty to get it). If not, can you advise which version of the OS will be the first to take 1.11 please? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1316970/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
