cathleen, are you interested?
Is this a networking feature?
we have lots of footprint analysis/reduction work need be done. This is a feature, and we won't be able to get to. i welcome any volunteers.
I don't this this is networking related. I'm setting it to XPCOM as a better choice. I would rather see this as a component which could return information (amount of memory allocated, number of XPCOM objects, Memory cache size, ...). Then, this could be added to the UI where appropriate (or maybe just let extensions show that information). Would the overhead of adding counters to malloc/free and XPCOM allocations be tolerable for this to be enabled in optimized builds?
This is probably a duplicate of bug 392351 (or it could that that API to show memory information in about|help).
hrm, I can't type in this bug. s/could that that/could use that/.
Should we replicate the "about:memory" feature implemented in Google Chrome? (see attached screen shot)
about:memory is available in FireFox 3.6.3 right? But this bug still indicates NEW status!!!
We now have about:memory, and various tracking bugs for improving it further (eg. bug 563700).