dbus-cpp

Dbus-c++ leaks memory

Bug #1396985 reported by Jussi Pakkanen on 2014-11-27

This bug affects 1 person

	Status	Importance	Assigned to	Milestone
Canonical System Image	Fix Released	High	Unassigned	Canonical System Image ww05-2015
dbus-cpp	Fix Released	High	Thomas Voß
dbus-cpp (Ubuntu)	Fix Released	Undecided	Unassigned

Bug Description

The sample program that comes with dbus-cpp (and thus presumably all clients of dbus-cpp) leaks memory quite badly. To test do this:

valgrind --tool=massif --trace-children=yes examples/benchmark/benchmark

Then view the result with massif-viewer. The image is attached and shows that memory consumption keeps on increasing all the time and never drops. Presumably because dbus-cpp is not properly releasing resources in libdbus-1.

Related branches

lp://staging/~thomas-voss/dbus-cpp/fix-1396985

Merged into lp://staging/dbus-cpp at revision 92

PS Jenkins bot: Approve (continuous-integration) on 2014-11-27

Antti Kaijanmäki (community): Approve on 2014-11-27

lp://staging/ubuntu/vivid-proposed/dbus-cpp

Revision history for this message

Jussi Pakkanen (jpakkane) wrote on 2014-11-27:

dbuscpp-massif.png Edit (415.3 KiB, image/png)

Thomas Voß (thomas-voss) on 2014-11-27

Changed in dbus-cpp:
assignee:	nobody → Thomas Voß (thomas-voss)
status:	New → In Progress
importance:	Undecided → High

Pat McGowan (pat-mcgowan) on 2015-01-23

Changed in canonical-devices-system-image:
importance:	Undecided → High
milestone:	none → ww05-2015
status:	New → In Progress

Revision history for this message

Launchpad Janitor (janitor) wrote on 2015-01-23:

This bug was fixed in the package dbus-cpp - 4.3.0+15.04.20150123-0ubuntu1

---------------
dbus-cpp (4.3.0+15.04.20150123-0ubuntu1) vivid; urgency=low

  [ thomas-voss ]
  * We ref on construction, so decrement the ref count by 1 to 1 prior
    to returning. (LP: #1396985)
-- Ubuntu daily release <email address hidden> Fri, 23 Jan 2015 09:56:06 +0000

Changed in dbus-cpp (Ubuntu):
status:	New → Fix Released

Revision history for this message

Selene ToyKeeper (toykeeper) wrote on 2015-01-25:

Having trouble testing this in place on the phone. Any hints on what process(es) to measure or how to make it leak? I didn't see any memory increase in any of the processes I checked.

Pat McGowan (pat-mcgowan) on 2015-01-28