Xubuntu 16.04.1 x86_64
uptime: 7 days
/usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0
/usr/lib/x86_64-linux-gnu/xfce4/panel/plugins/libindicator-plugin.so 454M (RES
via htop)
I think the problem with libindicator-plugin.so still exists.
--
You received this bug notification because you are
xubuntu 14.04 xfce (libindicator-plugin.so)
indicator-multiload memory leak still present.
System has been up for 7 days and 13 hours and memory usage is 1373MB.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
Related "indicator-multiload causes a memory leak in compiz when run under
unity" #779717 bug contains the similar information but has the higher bug heat
value. No fix for the indicator-multiload there though.
BTW the solution provided here (restart on big memory consumption) is actually
a work
** Changed in: unity-2d (Ubuntu)
Status: Confirmed => Invalid
** Changed in: unity
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/905854
Title:
memory leak
Please use the version at ppa:indicator-multiload/stable-daily or in
Ubuntu 13.04, there this is more or less fixed (restart on excessive
leaks).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/905854
T
This happens for me in Ubuntu 12.04 Precise on amd64.
indicator-multiload version 0.2-0ubuntu1.
After a month it was using >7G of ram.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/905854
Title:
mem
** Branch linked: lp:ubuntu/indicator-multiload
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/905854
Title:
memory leak in unity-2d-panel and indicator-multiload
To manage notifications about this
This bug was fixed in the package indicator-multiload - 0.3-0ubuntu1
---
indicator-multiload (0.3-0ubuntu1) raring; urgency=low
* New upstream release.
* Fixes LP: #926399, #823141, #891428, #905854, #962646, #1015623.
* debian/patches: Remove ensure_dirs_exist.patch, fixed upst
** Changed in: indicator-multiload
Status: Confirmed => Fix Released
** Changed in: indicator-multiload (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
I don't know whether there exists a bug for this precise problem.
Relevant valgrind logs are at
https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/905854/comments/26 and
https://bugs.launchpad.net/indicator-multiload/+bug/1101810/comments/5.
I will implement sth. to restart the indicator if
So what is the bug number for the libappindicator bug? We should be
commenting on that one and marking it as affecting us to increase the
priority/heat
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/905
I fear there is nothing that can be done from the indicator side. The
leak is related to the dbus communication, which is done by
libappindicator.
** Changed in: indicator-multiload
Importance: Undecided => Low
** Changed in: indicator-multiload
Status: New => Confirmed
--
You receive
I also see similar issue and found the bug report here.
If I kill the multload indicator and restart it, the system memory consumption
restored to normal level.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
It's affects me too on precise with all updates.
PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND
7114 db20 0 1240m 531m 36m R 25 16.3 375:53.06 firefox
29088 db20 0 460m 151m 16m R
@smoser,
The runaway process was indicator-mutli as it was the process consuming the
most memory (5.7G) in one case.
FWIW, I've also run valgrind on indicator-multiload using:
G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck
--leak-check=full --num-callers=40 --track-origin
Chris,
What is the runaway process when you see this in unity ? The subject just
says unity-2d-panel because that is the process that was showing the massive
footprint in unity-2d. We should update the subject and/or description.
Also, for anyone looking to actually debug the leak, there appe
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libdbusmenu (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/905854
Title:
** Also affects: libdbusmenu (Ubuntu)
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/905854
Title:
memory leak in unity-2d-panel and indicator-multiload
T
Also I'm not sure unity-2d is realted, I've been able to reproduce this
issue in regular unity. And on raring/quantal/precise.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/905854
Title:
memory leak
This may be a duplicate:
https://bugs.launchpad.net/indicator-multiload/+bug/1030293
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/905854
Title:
memory leak in unity-2d-panel and indicator-multiload
I'm also STILL affected by this... 12.10 64bit.
Changing the width of the indicator-multiload to 30 pixels does not help.
Increasing the update interval makes things worse.
This has been around since May-2011. Too bad it's still untackled...
--
You received this bug notification because you are
Noticed this morning that my desktop wa rather slow. according to atop
indicator-multiload is using vsize 7.3G, rsize 3.2G.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/905854
Title:
memory leak in
Well I finally decided to report this bug and here it is. :/ darn shame
that no fix has been submitted yet. I enjoy this indicator very much and
the alternative is just lacking in functionality.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
@Kevin:
If that's the case, then there's an easy workaround. In the preferences,
it's possible to remove all the status information from the menu, which
I've done since I considered it distracting. I haven't observed any
leaks since that time.
** Also affects: libdbusmenu-qt
Importance: Undeci
> Not sure if we could run some tools like valgrind on these processes
to see where the leak is occurring.
That's been done in bug 956810, which was marked as a duplicate of this
one. I do believe the leak is in libdbusmenu. It shows up in
indicator-multiload because the indicator changes its me
I just hit this after 18 days of uptime wondering what the heck was eating my
memory:
3173 arges 20 0 6669m 5.7g 3400 S1 36.8 274:43.01 indicator-multi
Not sure if we could run some tools like valgrind on these processes to
see where the leak is occurring.
--
You received this bu
also affects unity and not only 2d. workaround so far is do not use
indicator-multiload or kill process and keep restarting if you do need
to use it.
** Project changed: unity-2d => unity
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
how is this bug different from bug 1049282 & bug 956810?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/905854
Title:
memory leak in unity-2d-panel and indicator-multiload
To manage notifications ab
Just wanted to add another confirmation to the thread. I'm using 12.04
with Unity 2D, and indicator-multiload uses over 1 GB RAM after the
weekend. Killing it frees all the memory, and I relaunch it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
Dave,
That bug is marked fix-released in unity and ubuntu. Its possible that bug
779717 was incorrectly marked as fix-released (ie, not actually tested). But
rather than appending information to a fixed bug, this bug should track future
work.
Regarding 12.04 with indicator multiload causi
I have this issue as well on 12.04 beta. Indicator-multiload gets to
1.3GB of memory over a single weekend.
Is this bug a duplication of this bug?
https://bugs.launchpad.net/indicator-multiload/+bug/779717
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I suspect there is about zero percent chance of this being fixed, right?
it basically means you cannot run (at least I cannot run) indicator-multiload
unless you're logging in and out frequently.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
** 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/905854
Title:
memory leak in unity-2d-panel and indicator-multiload
To
** Changed in: unity-2d
Milestone: 5.2.1 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/905854
Title:
memory leak in unity-2d-panel and indicator-multiload
To manage notifications about
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/905854
I went without indicator-multiload for several days and did not see significant
increase in memory.
I turned it back on yesterday, and it is now 120M RES in top. So, this is
almost certainly caused by indicator-multiload.
I've added the ubuntu package for indicator-multiload to this bug.
$ u2dp
Chatting on IRC, we still suspect a leak could exist, so we'll do a
little profiling on unity-2d-panel to check.
** Changed in: unity-2d
Status: New => Confirmed
** Changed in: unity-2d
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubu
ok, so over probably 24 hours, I had RES sitting at 33M or so. So I do
suspect that the really bad leak is a result of indicator-multiload.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/905854
Title:
after letting this run for ~ 6 hours, i have /proc//statm output for
almost that entire time.
I'm now seeing a 'top' report of:
PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND
7473 smoser20 0 562m 64m 26m S0 1.7 0:07.32 unity-2d-places
5382 sm
In #ayatana [1] It was suggested that indicator-multiload might be
related, and requested that I see if the problem still arises. there was
previously a bug in this area that is marked fix-released (bug 779717).
So, I've disabled indicator-multiload, logged out, and logged back in.
Upon login, to
** Changed in: unity-2d
Milestone: None => 5.2.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/905854
Title:
memory leak in unity-2d-panel
To manage notifications about this bug go to:
https://
$ dpkg-query --show unity-2d-panel
unity-2d-panel 5.2.0-0ubuntu1
top shows
PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND
3936 smoser20 0 1989m 1.2g 20m S 32 31.3 229:41.50 firefox
2951 smoser20 0 726m 285m 8232 S1 7.3 30:36.6
** Changed in: unity-2d (Ubuntu)
Status: In Progress => Confirmed
** Changed in: unity-2d (Ubuntu)
Assignee: Scott Moser (smoser) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
** Changed in: unity-2d (Ubuntu)
Importance: Undecided => High
** Changed in: unity-2d (Ubuntu)
Status: New => In Progress
** Changed in: unity-2d (Ubuntu)
Assignee: (unassigned) => Scott Moser (smoser)
--
You received this bug notification because you are a member of Ubuntu
Bugs
I left the system basically un-used, over night, came back to it and now
i'm showing 780M resident, and 1280M virtual.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/905854
Title:
memory leak in unit
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/905854
Title:
memory leak in unity-2d-panel
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/905854
46 matches
Mail list logo
