Leak after opening and closing Minefield

RESOLVED FIXED

Status

()

Core
General
RESOLVED FIXED
10 years ago
10 years ago

People

(Reporter: Alex Polvi, Unassigned)

Tracking

({memory-leak})

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

10 years ago
Created attachment 306774 [details]
leak log

Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-US; rv:1.9b4pre) Gecko/2008030104 Minefield/3.0b4pre

Found one leak just by opening and closing the latest nightly. While my hunch says this is just weird garbage collection issues -- it should probably be addressed if we want to teach people how to do memory leak testing.

We launched Minefield, created a fresh profile, let the tabs load, and immediately closed the browser via a cmd-Q and selected "Save & Quit".

Output from leak-gauge:

Results of processing log nspr.log :
Leaked outer window e11d150 at address e11d150.
Leaked content nodes associated with node info manager at address 585970.

Summary:
Leaked 1 out of 4 DOM Windows
Leaked 0 out of 16 documents
Leaked 0 out of 2 docshells
Leaked content nodes in 1 out of 18 documents


Go beavs.
Attachment #306774 - Attachment mime type: application/octet-stream → text/plain
(Reporter)

Comment 1

10 years ago
Seems to have been resolved. 

Results of processing log nspr.log :

Summary:
Leaked 0 out of 6 DOM Windows
Leaked 0 out of 18 documents
Leaked 0 out of 3 docshells
Leaked content nodes in 0 out of 20 documents

yay!
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.