Open Bug 471458 Opened 12 years ago Updated 2 years ago

Memory leak of document with mousemove event and tooltip

Categories

(Core :: DOM: Core & HTML, defect, P5)

x86
Windows XP
defect

Tracking

()

REOPENED

People

(Reporter: martijn.martijn, Unassigned)

Details

(Keywords: memory-leak, testcase)

Attachments

(1 file)

See testcase, which gives me this memory leak of a document in current trunk build, according to the nspr log.

Results of processing log leak1.log :
Leaked document at address 3e9d400.
 ... with URI "jar:file:///C:/Documents%20and%20Settings/mw/Bureaublad/moz/firefox20081229/chrome/toolkit.jar!/content/global/bindings/popup.xml".
 ... with URI "chrome://global/content/bindings/popup.xml".
Leaked content nodes associated with node info manager at address 3f3fdc0.
Leaked content nodes associated with node info manager at address 3f780d0.
Leaked content nodes associated with node info manager at address 2fcd250.
 ... with document URI "jar:file:///C:/Documents%20and%20Settings/mw/Bureaublad/moz/firefox20081229/chrome/toolkit.jar!/content/global/bindings/popup.xml".
 ... with document URI "chrome://global/content/bindings/popup.xml".

Summary:
Leaked 0 out of 0 DOM Windows
Leaked 1 out of 1443 documents
Leaked 0 out of 5 docshells
Leaked content nodes in 3 out of 2159 documents
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WORKSFORME
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Priority: -- → P5
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.