Closed Bug 324796 Opened 19 years ago Closed 16 years ago

Memory leak at www.jigzone.com

Categories

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

x86
Windows XP
defect
Not set
normal

Tracking

()

VERIFIED WORKSFORME

People

(Reporter: ria.klaassen, Assigned: sayrer)

References

()

Details

(Keywords: memory-leak)

I get this result after loading the java puzzle: Leaked outer window 1d07ec0 at address 1d07ec0. Leaked inner window 21a53b8 (outer 1d07ec0) at address 21a53b8. ... with URI "http://www.jigzone.com/z.php?k=2F4GIDD8". Summary: Leaked 2 out of 16 DOM Windows Leaked 0 out of 34 documents Leaked 0 out of 7 docshells
blocks bug 320915?
Might this bug be related to https://bugzilla.mozilla.org/show_bug.cgi?id=331684 ? It would be interesting to test if this testcase leaked: http://www.jigzone.com/xmockup/bugs/resizeTestFF.php But this testcase did not: http://www.jigzone.com/xmockup/bugs/resizeTestFFStatic.php
Assignee: general → sayrer
After installing the new Java Plug-in as instructed in bug 298852 comment 14, I can no longer reproduce this problem using Firefox 3 beta 2 on Windows XP. Previously, I was able to reproduce using the same version of Firefox. Can anyone else still reproduce with the new Java Plug-in? If so, what OS and version of Firefox?
There was already a check mark in the "Mozilla family" check box, as well as in "Check for Updates Automatically" in the Update tab. I tried a puzzle of an owl and I get the following result: Leaked outer window 2668748 at address 2668748. Leaked inner window 2872f20 (outer 2668748) at address 2872f20. ... with URI "http://www.jigzone.com/puzzles/17055D51BD10?z=0". Summary: Leaked 2 out of 24 DOM Windows Leaked 0 out of 58 documents Leaked 0 out of 10 docshells
Did you check the checkbox to enable the next-generation Java Plug-In? Did you restart Firefox? What version of Firefox and what OS are you using?
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
Status: RESOLVED → VERIFIED
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.