Changes

Jump to: navigation, search

Performance:Leak Tools

1,140 bytes removed, 23:40, 27 October 2014
Leak tools for simple objects and summary statistics
Generate a trace-malloc dump by building with <code>ac_add_options --enable-trace-malloc</code> and then passing <code>--trace-malloc FILENAME</code> when you start Firefox.
==== Valgrind , LSAN and Apple tools ====
[http://valgrind.org/ Valgrind] is a free tool for Linux and Mac that detects various kinds of memory-related errors at runtime, including leaks. Documentation These are documented on how to use it with Mozilla code is [https://developer.mozilla.org/en-US/docs/Mozilla/Testing/Valgrind here]. Valgrind is used as [https://developer.mozilla.org/en-US/docs/Valgrind_test_job part] of Mozilla's continuous integration testing, though the coverage is limited because Valgrind is slow. ==== LSAN ====[https://code.google.com/p/address-sanitizer/wiki/LeakSanitizer LeakSanitizer] (a.k.a. LSAN) is similar to Valgrind, but it runs faster because it uses static source code instrumentation. LSAN is part of Mozilla's continuous integration testing, with most tests running through it as part of the AddressSanitizer (a.k.a. ASAN) test jobs. ==== Apple tools ==== Apple provides [http://developer.apple.com/documentation/Performance/Conceptual/ManagingMemory/Articles/FindingLeaks.html some toolsMDN] for Mac OS X that probably report similar problems to those reported by LSAN and Valgrind. The "leaks" tool is not recommended for use with SpiderMonkey or Firefox, because it gets confused by tagged pointers and thinks objects have leaked when they have not (see {{bug|390944}}).
=== Leak tools for debugging memory growth that is cleaned up on shutdown ===
Confirm
1,345
edits

Navigation menu