680649 - inspector leaks iframe [chrome://browser/content/inspector.html] until shutdown

Status: RESOLVED FIXED

(DevTools :: General, defect)

Description

[Tim Taubert [:ttaubert] (inactive)]

leak statistics:

[browser/base/content/test/inspector/browser_inspector_registertools.js]
  1x [data:text/html,registertool%20tests%20for%20inspector]
  2x [chrome://browser/content/inspector.html]
  1x [about:blank]

[browser/base/content/test/inspector/browser_inspector_tab_switch.js]
  3x [chrome://browser/content/inspector.html]

[browser/base/content/test/inspector/browser_inspector_bug_665880.js]
  2x [chrome://browser/content/inspector.html]

[browser/base/content/test/inspector/browser_inspector_highlighter.js]
  1x [chrome://browser/content/inspector.html]

[browser/base/content/test/inspector/browser_inspector_iframeTest.js]
  1x [chrome://browser/content/inspector.html]

[browser/base/content/test/inspector/browser_inspector_initialization.js]
  1x [chrome://browser/content/inspector.html]

[browser/base/content/test/inspector/browser_inspector_scrolling.js]
  1x [chrome://browser/content/inspector.html]

[browser/base/content/test/inspector/browser_inspector_treePanel_output.js]
  1x [chrome://browser/content/inspector.html]

[browser/base/content/test/inspector/browser_inspector_treeSelection.js]
  1x [chrome://browser/content/inspector.html]

Comment 1

[Tim Taubert [:ttaubert] (inactive)]

Attachment: patch v1

Comment 2

[Panos Astithas (he/him) [:past] (please ni?)]

Tim, how did you manage to get those statistics? If it's a tool, it seems pretty useful!

Comment 3

[Tim Taubert [:ttaubert] (inactive)]

Attachment: debug build log parser (script)

(In reply to Panos Astithas [:past] from comment #2)
> Tim, how did you manage to get those statistics? If it's a tool, it seems
> pretty useful!

That's a little Python script I wrote yesterday. It's pretty messy and my Python skills are not the best but it does the job! :)

It parses debug build logs (only) and counts created and discarded DOMWindows and assigns them to tests and urls to the DOMWindows. All the information is already contained in the build log so all it does is parse the file.

./parse.py debug-build-log.txt > leak-output.txt

Comment 4

[Tim Taubert [:ttaubert] (inactive)]

http://hg.mozilla.org/integration/fx-team/rev/d827ae445f33

Comment 5

[Tim Taubert [:ttaubert] (inactive)]

http://hg.mozilla.org/mozilla-central/rev/d827ae445f33