g_dbus memory leak in lrmd
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pacemaker (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Trusty |
Fix Released
|
Medium
|
Guilherme G. Piccoli |
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:/
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:/
[Original Description]
I'm running Pacemaker 1.1.10+
The details of the bug are covered here in this thread (http://
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?
description: | updated |
Changed in pacemaker (Ubuntu): | |
assignee: | nobody → Seyeong Kim (xtrusia) |
assignee: | Seyeong Kim (xtrusia) → nobody |
tags: | added: sts |
tags: | added: sts-sru-needed |
description: | updated |
Changed in pacemaker (Ubuntu): | |
status: | Confirmed → Fix Released |
Changed in pacemaker (Ubuntu Trusty): | |
assignee: | nobody → Seyeong Kim (xtrusia) |
importance: | Undecided → Medium |
status: | New → In Progress |
tags: | added: sts-sponsor-ddstreet |
description: | updated |
Changed in glib2.0 (Ubuntu Trusty): | |
assignee: | nobody → Seyeong Kim (xtrusia) |
description: | updated |
description: | updated |
Changed in pacemaker (Ubuntu Trusty): | |
assignee: | Seyeong Kim (xtrusia) → Guilherme G. Piccoli (gpiccoli) |
Status changed to 'Confirmed' because the bug affects multiple users.