The Mozilla
Organization
Our Mission
Who We Are
Getting Involved
Community
Editorials
What's New
Newsbot
Development
Roadmap
Module Owners
Blue Sky
Projects
Status
Tools
Products
Source Code
Binaries
Documentation
License Terms
Bug Reports
Quality
Search
Feedback


performance: tools

Contact: Chris Waterson (waterson@netscape.com)
$Id: tools.html,v 1.3 1999/05/17 17:06:34 waterson%netscape.com Exp $

Memory Leaks

The following tools are used to track down memory leaks in the product.

  • Rational Purify®. (Commercial)

  • LeakTracer.

  • ccmalloc.

  • debauch.

  • memwatch.

  • ElectricFence.

  • Leaky. This is a home-grown tool that Kipp put together:

      "Its a tool called leaky. What it does it help you track down memory leaks and some kinds of memory corruption. It also has entry pointers for logging addref/release calls. The key thing that leaky does is this: it logs all calls to malloc/free/realloc/new/delete into a log file. The logging data includes information about size and address, as well as the *call stack of the operation*. The leaky program then can translate the call stack data from addresses into symbols and then dump the data out." *

Profiling

The following tools are used to measure product performance.

  • Rational Quantify. (Commercial)

  • hiprof. A hierarchical instruction profiler for Digital Unix. There is an online tutorial, courtesy Jim Nance (jim_nance@yahoo.com):

      "I like it because it does not require you to recompile the program, because it give accurate times for callers, and because it comes with DU so that everyone developing there should already have it." *

  • gprof. There are rumors that this has trouble with dynamically linked and loaded objects (like Mozilla).



Copyright © 1998 The Mozilla Organization.