Closed Bug 352915 Opened 19 years ago Closed 18 years ago

Memory leak at metacafe.com

Categories

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

Product:
Core
Component:
DOM: Core & HTML
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: schapel, Unassigned)

References

(
URL
)

Details

(Keywords: memory-leak)

Reproducible: Always Steps to Reproduce: 1. Go to http://www.metacafe.com/watch/79042/mr_bean_stairs/ After opening the URL with Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060911 Minefield/3.0a1, the leak gauge reports: Leaked inner window 1a48200 (outer 22de218) at address 1a48200. ... with URI "http://www.metacafe.com/watch/79042/mr_bean_stairs/". Leaked inner window 278ab00 (outer 22de218) at address 278ab00. ... with URI "http://www.mozilla.org/projects/minefield/". Leaked outer window 22de218 at address 22de218. Leaked document at address 1f6fe58. ... with URI "http://www.mozilla.org/projects/minefield/". Leaked document at address 212a5e8. ... with URI "http://www.metacafe.com/watch/79042/mr_bean_stairs/". Summary: Leaked 3 out of 8 DOM Windows Leaked 2 out of 39 documents Leaked 0 out of 3 docshells
WFM, Mac trunk debug. Steve, are you still seeing this?
Heh, Mr. Bean. Oh, right, leak-gauge.pl now reports 0 leaks. Good work!
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → WORKSFORME
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.