Last Comment Bug 659860 - (mlk-fx7) [meta] Leaks and quasi-leaks reported against Firefox 7
: [meta] Leaks and quasi-leaks reported against Firefox 7
: meta, mlk
Product: Core
Classification: Components
Component: General (show other bugs)
: unspecified
: All All
-- normal with 5 votes (vote)
: ---
Assigned To: Nicholas Nethercote [:njn]
Depends on: 657115 661467 505108 653936 654573 mlk-fx6 660577 662464 662649 664630 666058 666221 ZombieCompartments 668881 669240
Blocks: mlk-fx8
  Show dependency treegraph
Reported: 2011-05-25 21:42 PDT by Nicholas Nethercote [:njn]
Modified: 2014-10-25 13:16 PDT (History)
42 users (show)
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---


Description User image Nicholas Nethercote [:njn] 2011-05-25 21:42:12 PDT
This bug is for tracking leaks and quasi-leaks reported against Firefox 7 (at any stage in the nightly/aurora/beta/release cycle).                       
Leaks reported against earlier versions that have been confirmed to still be present in this version can also be tracked here.             
Leak reports against this version that lack sufficiently specific information may be marked as duplicates of this tracking bug.
Comment 1 User image Ahmed Aly 2011-06-16 06:48:18 PDT
could this help with detecting memory leaks for firefox ?
Comment 2 User image Nicholas Nethercote [:njn] 2011-06-16 17:14:14 PDT
(In reply to comment #1)
> could this help with detecting memory leaks for firefox ?

No.  Read that page carefully -- that tool doesn't detect leaks, just buffer overruns/underruns and use-after-free errors.  It's basically a cut-down, faster version of Valgrind and we already use Valgrind.
Comment 3 User image Nicholas Nethercote [:njn] 2011-07-27 16:01:22 PDT
This tracking bug has reached the end of its useful life.  All the still 
open blocking bugs have had their whiteboards marked with "MemShrink", and 
so will be tracked that way by the MemShrink project.

Note You need to log in before you can comment on or make changes to this bug.