Comment 5 for bug 905854

after letting this run for ~ 6 hours, i have /proc/<pid>/statm output for almost that entire time.
I'm now seeing a 'top' report of:
  PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
 7473 smoser 20 0 562m 64m 26m S 0 1.7 0:07.32 unity-2d-places
 5382 smoser 20 0 571m 51m 26m S 0 1.3 0:41.79 unity-2d-launch
 5423 smoser 20 0 396m 37m 9m S 8 1.0 1:01.63 unity-panel-ser
 5381 smoser 20 0 507m 35m 20m S 2 0.9 0:49.17 unity-2d-panel

So it seems I've jumped in RES memory by 5M. statm now looks like:
130041 9374 5327 10 0 39430 0

the log that i have of statm output is generally pretty stable except for:
2012-01-19 19:33:10: 113405 8771 5326 10 0 22794 0
2012-01-19 19:34:10: 113405 8771 5326 10 0 22794 0
2012-01-19 19:35:10: 129789 9100 5326 10 0 39178 0
2012-01-19 19:36:10: 129789 9239 5326 10 0 39178 0

At that point the 'data + stack' (see man proc) increased dramatically. I'm not sure whether or not that correlated with the growth in RES. I really need to read more on memory use, I'm not sure all this is that useful.

However, in a nutshell, my memory footprint reported by 'RES' in top did climb 5M over the course of 6 hours *without* indicator-multiload running.