how is this bug different from bug#905854 bug#1049282
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/956810
Title:
Small memory leak (~200 KiB/h)
To manage notifications about this bug go to:
*** This bug is a duplicate of bug 905854 ***
https://bugs.launchpad.net/bugs/905854
** This bug has been marked a duplicate of bug 905854
memory leak in unity-2d-panel and indicator-multiload
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
What's the status of this bug? Is it slated for a fix in an upcoming
release?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/956810
Title:
Small memory leak (~200 KiB/h)
To manage notifications
Hi, I'm currently seeing ~1GB memory usage, which I noted on #1030293.
Are these two bugs duplicates?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/956810
Title:
Small memory leak (~200 KiB/h)
To
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: indicator-multiload (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/956810
I confirmed with massif that the libdbusmenu menuitem_property_idle
function in htorque's valgrind traceback allocating the bulk of the
memory in the process and it increases linearly with time. See
https://bugs.launchpad.net/ubuntu/+source/libdbusmenu/+bug/784808/comments/3
--
You received
** Also affects: indicator-multiload
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/956810
Title:
Small memory leak (~200 KiB/h)
To manage notifications
Okay, bug 784808 was instructive, but I think that one really _was_
resolved and it's a related (but not _exactly_ the same) issue we're
dealing with here. I suspect the culprit is this patch
http://bazaar.launchpad.net/~dbusmenu-
team/dbusmenu/trunk.0.6/revision/362.4.1 to libdbusmenu.
It adds
The filenames in that valgrind stack don't match those in the indicator-
multiload source I have. They seem to all be standard glib files. Not
sure if that narrows things down at all.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
the menuitem_property_idle - g_variant_parse bits make it sound like
bug LP #784890, but that was marked fixed in libdbusmenu
(0.4.90-0ubuntu1) oneiric;
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
FYI I'm also seeing a major leak in Precise. Went on vacation for 4
days and indicator-multiload was using ~5GB!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/956810
Title:
Small memory leak (~200
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/956810
Title:
Small memory leak (~200 KiB/h)
To manage notifications about this bug go to:
12 matches
Mail list logo
