Filed by: philringnalda [at] gmail.com https://treeherder.mozilla.org/logviewer.html#?job_id=75774324&repo=autoland https://archive.mozilla.org/pub/firefox/tinderbox-builds/autoland-win64-debug/1486602501/autoland_win8_64-debug_test-mochitest-e10s-browser-chrome-4-bm109-tests1-windows-build145.txt.gz
Well, that escalated quickly. At the same time I saw that single intermittent on autoland I filed this from, I was pushing a simulation of trunk-as-aurora, as though we'd done the merge that will happen 2017-03-06, to try, and I got https://treeherder.mozilla.org/#/jobs?repo=try&revision=193150ee5e4a2c7314a5b2d6f4c3281dff695683&group_state=expanded&selectedJob=75777763 with this leak being permaorange. Conveniently, that'll let you push to try on top of those two trunk-as-aurora patches, enabling the tests that bug 1337401 enabled just one at a time until you get the leak (or, disabling them one at a time until you no longer get the leak). Inconveniently, you've only got 3.5 weeks to get that done and get the leaking one, if it's just one, disabled before the merge. [Tracking Requested - why for this release]: permaorange on the merge to aurora, closed trees, tearing of hair.
status-firefox51: --- → unaffected
status-firefox52: --- → unaffected
status-firefox53: --- → unaffected
status-firefox54: --- → affected
status-firefox-esr45: --- → unaffected
status-firefox-esr52: --- → unaffected
tracking-firefox54: --- → ?
Summary: Intermittent leakcheck | tab process: 10016 bytes leaked (Accessible, HyperTextAccessible, HyperTextAccessibleWrap, Mutex, nsStringBuffer, ...) → Intermittent on trunk, permaorange when Gecko 54 merges to aurora leakcheck | tab process: 10016 bytes leaked (Accessible, HyperTextAccessible, HyperTextAccessibleWrap, Mutex, nsStringBuffer, ...)
Tracking 54+ for the permaorange potential.
tracking-firefox54: ? → +
Well, that was easy enough, https://treeherder.mozilla.org/#/jobs?repo=try&revision=3fcc9a82f626e98888540545fe44290895b5f016&group_state=expanded Dunno whether it's leaking because Win8, or leaking because Win64, so I'll just disable it on all Windows debug and let you sort it out.
status-firefox54: affected → disabled
Whiteboard: [test disabled on Windows debug]
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/mozilla-inbound/rev/549115eef1f6 disable browser_caching_name.js on Windows debug for leaks
8 failures in 836 pushes (0.01 failures/push) were associated with this bug in the last 7 days. Repository breakdown: * mozilla-inbound: 4 * autoland: 3 * try: 1 Platform breakdown: * windows8-64: 8 For more details, see: https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1338034&startday=2017-02-06&endday=2017-02-12&tree=all
You need to log in before you can comment on or make changes to this bug.