Comment 8 for bug 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=$(pidof unity-2d-panel)
$ cat /proc/$u2dp/statm
140018 30931 2236 10 0 49395 0
$ cat /proc/$u2dp/status
Name: unity-2d-panel
State: S (sleeping)
Tgid: 9109
Pid: 9109
PPid: 8987
TracerPid: 0
Uid: 1000 1000 1000 1000
Gid: 1000 1000 1000 1000
FDSize: 64
Groups: 4 20 24 46 116 118 124 127 133 1000
VmPeak: 583612 kB
VmSize: 560356 kB
VmLck: 0 kB
VmPin: 0 kB
VmHWM: 124364 kB
VmRSS: 124136 kB
VmData: 197728 kB
VmStk: 136 kB
VmExe: 40 kB
VmLib: 74420 kB
VmPTE: 904 kB
VmSwap: 3252 kB
Threads: 2
SigQ: 0/30610
SigPnd: 0000000000000000
ShdPnd: 0000000000000000
SigBlk: 0000000000000000
SigIgn: 0000000000001000
SigCgt: 0000000180010000
CapInh: 0000000000000000
CapPrm: 0000000000000000
CapEff: 0000000000000000
CapBnd: ffffffffffffffff
Cpus_allowed: f
Cpus_allowed_list: 0-3
Mems_allowed: 00000000,00000001
Mems_allowed_list: 0
voluntary_ctxt_switches: 3239988
nonvoluntary_ctxt_switches: 848856