Closed
Bug 324817
Opened 18 years ago
Closed 18 years ago
[mlk] Memory Leak with NoScript 1.1.3.8 extension
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: stevee, Unassigned)
Details
(Keywords: memory-leak)
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a1) Gecko/20060125 Firefox/1.6a1 ID:2006012517 1. New profile 2. Run firefox 3. Tools > Options > General ; set Homepage to www.cnn.com 4. Install NoScript v1.1.3.8 extension from https://addons.mozilla.org/extensions/moreinfo.php?id=722&application=firefox 5. Restart firefox (with your homepage set to www.cnn.com) 6. Note the yellow NoScript bar at the bottom of the screen. Click on Options and choose "Allow cnn.com" (page then reloads) 7. Close firefox and analyse nspr.log Summary: Leaked 6 out of 8 DOM Windows Leaked 21 out of 27 documents Leaked 0 out of 3 docshells
Reporter | ||
Comment 1•18 years ago
|
||
Note: NoScript is the 2nd most popular extension from addons.mozilla.org with (currently) 210199 downloads.
Comment 2•18 years ago
|
||
Looking into it.
Comment 3•18 years ago
|
||
Checked, verified and corrected in NoScript 1.1.3.9 Resolving as "INVALID", because it's not a Firefox bug. Many thanks Steve, I've credited you in the NoScript changelog.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → INVALID
Reporter | ||
Comment 4•18 years ago
|
||
Thanks for the quick response Giorgio!
Reporter | ||
Comment 5•18 years ago
|
||
Much better! But I still get Leaked inner window 2193b98 (outer 20dc850) at address 2193b98. ... with URI "http://www.cnn.com/". Leaked outer window 20dc850 at address 20dc850. Summary: Leaked 2 out of 7 DOM Windows Leaked 0 out of 25 documents Leaked 0 out of 3 docshells (same repo steps) now with 1.1.3.9 - is this expected?
Comment 6•18 years ago
|
||
(In reply to comment #5) > Much better! But I still get > > Leaked inner window 2193b98 (outer 20dc850) at address 2193b98. > ... with URI "http://www.cnn.com/". > Leaked outer window 20dc850 at address 20dc850. > Summary: > Leaked 2 out of 7 DOM Windows > Leaked 0 out of 25 documents > Leaked 0 out of 3 docshells > > (same repo steps) now with 1.1.3.9 - is this expected? > Yes, it is known and expected. I've not observed it on cnn.com (I get 0 leaks), but I saw this consistently on other flash-intensive sites, and decided to release neverhteless because it looks like a cosmetic-only "leak": as soon as you close the tab or replace the document, those 2 "leaked" window references per document are actually released, with no real impact on memory pollution. I'll keep investigating anyway to see if I can make them releasable anyway on application quit (before the log is shut down), as I understand these "ghost leaks" can interfer with other diagnostic activities.
You need to log in
before you can comment on or make changes to this bug.
Description
•