Closed Bug 167035 Opened 19 years ago Closed 11 years ago

track memory usage and performance via help|about


(Core :: XPCOM, enhancement)

Not set





(Reporter: Marko.Macek, Unassigned)




(1 file)

It seems mozilla still has serious memory usage problems (I just restarted after
my mozilla had VM Size of 250M, despite just having 2 browsers + mail open)

It would be very useful for bug reports to have help|about show the status of
various memory allocators (current,max allocated).

another thing would be performance of the javascript GC, mostly average/maximum
cathleen, are you interested?
Assignee: dougt → cathleen
Component: XPCOM → Networking
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?
Assignee: cathleennscp → nobody
Component: Networking → XPCOM
QA Contact: scc → xpcom
Summary: track memory usage and performance in Help|About. → track memory usage and performance
Summary: track memory usage and performance → track memory usage and performance via help|about
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)
Blocks: 515354
No longer blocks: 515354
Depends on: 515354
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).
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.