github
Advanced Search
  • Home
  • Pricing and Signup
  • Explore GitHub
  • Blog
  • Login

toolness / memory-profiler

  • Admin
  • Watch Unwatch
  • Fork
  • Your Fork
  • Pull Request
  • Download Source
    • 3
    • 1
  • Source
  • Commits
  • Network (1)
  • Issues (0)
  • Downloads (1)
  • Wiki (1)
  • Graphs
  • Branch: master

click here to add a description

click here to add a homepage

  • Branches (1)
    • master ✓
  • Tags (1)
    • blog-post-1
Sending Request…
Enable Donations

Pledgie Donations

Once activated, we'll place the following badge in your repository's detail box:
Pledgie_example
This service is courtesy of Pledgie.

Memory Profiler Firefox extension — Read more

  cancel

https://wiki.mozilla.org/Labs/Memory_Profiler

  cancel
  • Private
  • Read-Only
  • HTTP Read-Only

This URL has Read+Write access

Run the cycle collector prior to memory profiling if possible, otherwise 
just run standard JS GC. 
Atul Varma (author)
Mon Oct 12 23:36:23 -0700 2009
commit  6ae559314da11b6cef1db439948e4b815710ad93
tree    a6cc039486d0791f549a467578d7671ef7e152ca
parent  442df18ab31353edd72ae771e02e65f66cc3c8f3
memory-profiler /
name age
history
message
file .hgignore Loading commit data...
file .hgtags
file README.txt Tue Oct 06 19:17:17 -0700 2009 Added a lot to README.txt. [Atul Varma]
file copy-files-from-jetpack.sh Sat Oct 03 16:42:19 -0700 2009 Added initial files, sans files from jetpack. [Atul Varma]
directory extension/
file manage.py
directory python-modules/ Sat Oct 03 16:42:19 -0700 2009 Added initial files, sans files from jetpack. [Atul Varma]
directory sample-pages/
README.txt
Installing Memory Profiler
--------------------------

To install Memory Profiler for development purposes to your default
Firefox profile, just enter the root directory of your Memory Profiler
source code checkout and run:

  python manage.py install

If you have a separate profile that you'd prefer to install the
extension under, such as 'testing', you can add that as an optional
parameter:

  python manage.py install --profile=testing

Building Binary Components
--------------------------

Pre-compiled binary components needed by Memory Profiler are kept in the
repository, so it's likely that you don't need to compile anything to
start using it. However, if a version of the components don't exist
for your OS and/or Gecko platform, you'll need to build them yourself.

To do this, you actually need to get Jetpack's source code and
compile its binary component, as Jetpack's binary components are
what power Memory Profiler.

So, you need to get Jetpack from here:

  http://hg.mozilla.org/labs/jetpack/

Make sure you clone this repository in a directory "parallel to"
Memory Profiler's directory. In other words, if this file is
located at /foo/memory-profiler/README.txt, then Jetpack's
README should be at /foo/jetpack/README.

Read Jetpack's README, and build its binary components. Then, go into
Memory Profiler's root directory and run:

  ./copy-files-from-jetpack.sh

This will copy the binary components from Jetpack's repository to the
proper location in Memory Profiler.

Using Memory Profiler
---------------------

Just go to the "Tools" menu and select "Memory Profiler".

Uninstalling Memory Profiler
--------------------

Just run "python manage.py uninstall", optionally specifying a profile
name if necessary, just like you did with the 'install' target.
Alternatively, you can also uninstall the extension through the normal
Firefox addon management UI.

Building an XPI
---------------

To build an XPI for Memory Profiler, just run:

  python manage.py xpi

More Information
----------------

More information on this project can be found here:

  https://wiki.mozilla.org/Labs/Memory_Profiler
Blog | Support | Training | Contact | API | Status | Twitter | Help | Security
© 2010 GitHub Inc. All rights reserved. | Terms of Service | Privacy Policy
Powered by the Dedicated Servers and
Cloud Computing of Rackspace Hosting®
Dedicated Server