Closed Bug 671543 Opened 13 years ago Closed 13 years ago

Additional chrome://browser/content/inspector.html leaks since specialpowers has been enabled for mochitest-browser-chrome

Categories

(Testing :: Mochitest, defect)

Product:
Testing
Component:
Mochitest
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: dao, Assigned: mccr8)

References

Details

(Keywords: regression, Whiteboard: [MemShrink:P2]) 

browser-chrome tests used to leak chrome://browser/content/inspector.html two times (see bug 658738). Starting with <http://hg.mozilla.org/mozilla-central/rev/5dfcc562b0a9>, we get 12 leaks.

Joel, any idea what's going on?
I verified that backing out 5dfcc562b0a9 on mozilla-central tip unregresses this.
thanks for the information here.  I have no idea why we would be leaking, but this is something that we need to look into.  

To clarify this is only in browser-chrome that we are seeing the leak?
I don't know. browser-chrome is all I'm looking at, because of bug 658738.
is this on a specific platform.  I looked at Linux Debug M-Oth, and I didn't see any leaks for mochitest-chrome or browser-chrome:
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1310600156.1310604126.17352.gz&fulltext=1
Look for *** End BrowserChrome Test Results ***, below that you'll find twelve lines like this one:

--DOMWINDOW == 300 (0x9df3070) [serial = 1269] [outer = 0xa646e58] [url = chrome://browser/content/inspector.html]
I am not able to reproduce this locally.  I have tried a debug and release builds on ubuntu 11.04.  No mention of inspector.html or similar looking things.  Also tried downloading builds from tinderbox instead of building locally with no luck.
Any update on this? This is persistent on Tinderbox. Did you see any DOM windows going away like the one mentioned in comment 5 (which I copied from the log in comment 4)? You should, since a bunch of windows must be around and close at the end of a browser-chrome run (e.g. browser.xul, browser-harness.xul, hiddenWindow.html). If you don't see them, you're doing something wrong.
Note that this cannot be seen with a release build. You need a debug build.
Ping?
I haven't been able to reproduce this on a debug build locally.  Any tips on how to reproduce this would be helpful.
I don't know what you're seeing or not seeing. Please reply to comment 7.
Whiteboard: [MemShrink]
so I am working on another patch in bug 676274 that will remove specialpowers from chrome and browser-chrome.  This should resolve this bug.
Depends on: 676274
Assignee: nobody → continuation
Whiteboard: [MemShrink] → [MemShrink:P2]
Fixed by bug 680649. However, it would still be interesting to know why specialpowers increased the leak count.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.