I don't see the bug here. As the description says, passing the result of
a g_variant_new() call (that is, a floating GVariant) as the third
argument to g_dbus_proxy_call() should be fine according to the docs:
If the parameters GVariant is floating, it is consumed. This allows
convenient 'inline'
Yes, I was running it using G_SLICE=always-malloc and G_DEBUG=gc-
friendly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/953970
Title:
Small memory leak
To manage notifications about this bug go
I'm running the service under valgrind again, and am not seeing that
leak anymore:
==20111== LEAK SUMMARY:
==20111==definitely lost: 0 (+0) bytes in 0 (+0) blocks
==20111==indirectly lost: 0 (+0) bytes in 0 (+0) blocks
==20111== possibly lost: 10,100 (-88) bytes in 158 (-2) blocks
Four hours later, nothing definitely or indirectly lost. Marking this
report as invalid.
** Changed in: indicator-application
Status: Incomplete = Invalid
** Changed in: indicator-application (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a
** Changed in: indicator-application
Importance: Undecided = Medium
** Changed in: indicator-application
Assignee: (unassigned) = Charles Kerr (charlesk)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: indicator-application
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/953970
Title:
Small memory leak
To manage notifications about this
