Labs/Memory Profiler: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(added more docs)
Line 13: Line 13:
You can access the tool by going to the "Tools" menu and selecting "Memory Profiler".
You can access the tool by going to the "Tools" menu and selecting "Memory Profiler".


= Building from Source =
= Getting The Source =


Running the extension from the source requires first getting the Jetpack source code here:
Just clone the HG repository:


   http://hg.mozilla.org/labs/jetpack/
   http://hg.mozilla.org/users/avarma_mozilla.com/memory-profiler/


You'll need to build the XPCOM component there. In a parallel directory to this repository, clone the Memory Profiler repository:
And then read the [http://hg.mozilla.org/users/avarma_mozilla.com/memory-profiler/file/tip/README.txt README].
 
  http://hg.mozilla.org/users/avarma_mozilla.com/memory-profiler/


= Understanding the Source =
= Understanding the Source =

Revision as of 03:03, 7 October 2009

Memory Profiler is an experimental Labs project that attempts to make debugging memory use in web pages easier.

For more information about the tool's design and rationale, see Atul's blog post entitled Web Application Memory Profiling, Take Two.

3988687880_7073e5b7e8_o.png

Installation and Use

The Firefox extension is available here:

 https://addons.mozilla.org/en-US/firefox/addon/14666/

You can access the tool by going to the "Tools" menu and selecting "Memory Profiler".

Getting The Source

Just clone the HG repository:

 http://hg.mozilla.org/users/avarma_mozilla.com/memory-profiler/

And then read the README.

Understanding the Source

For information on how to create your own custom memory profiling routines, check out the Jetpack Binary Components API.

See Atul's blog post entitled Fun with SpiderMonkey for information on how the memory profiler works.