Closed Bug 659860 (mlk-fx7) Opened 13 years ago Closed 13 years ago

[meta] Leaks and quasi-leaks reported against Firefox 7

Categories

(Core :: General, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: n.nethercote, Assigned: n.nethercote)

References

Details

(Keywords: memory-leak, meta)

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.
Depends on: 660577
Depends on: 661467
Depends on: 657115
Depends on: 662464
Depends on: 654573
Depends on: 505108
Depends on: 664630
Depends on: 653936
http://blog.chromium.org/2011/06/testing-chromium-addresssanitizer-fast.html
could this help with detecting memory leaks for firefox ?
(In reply to comment #1)
> http://blog.chromium.org/2011/06/testing-chromium-addresssanitizer-fast.html
> 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.
Depends on: 662649
Depends on: 666221
Depends on: 666058
Depends on: 668881
Depends on: ZombieCompartments
Depends on: 669240
Blocks: mlk-fx8
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.
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.