Intermittent leakcheck | tab 37416 bytes leaked (APZEventState, ActiveElementManager, AtomSet, BackstagePass, BrowserChild, ...)
Categories
(Remote Protocol :: CDP, defect, P2)
Tracking
(Not tracked)
People
(Reporter: intermittent-bug-filer, Unassigned)
References
(Regression)
Details
(Keywords: intermittent-failure, regression, Whiteboard: [stockwell unknown])
#[markdown(off)]
Filed by: nbeleuzu [at] mozilla.com
https://treeherder.mozilla.org/logviewer.html#?job_id=242466222&repo=autoland
After the backout of Bug 1527287 , the leak changed from BrowsingContext to BrowserChild.
:eakhgari , can you please take a look?
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Updated•6 years ago
|
Comment 3•6 years ago
|
||
Ryan Hunt renamed this class in bug 1534395. If you want to blame someone for the object name changing in the leak report (just joking of course) it'd be him. ;-)
But of course this is the dupe of whatever bug was tracking the leak with the old name of the object (perhaps bug 1527087 but I am not sure.) Unccing myself because that is all I know here.
Comment 4•6 years ago
|
||
Ryan can you please take a look at this?
There are 146 failures in the last 7 days on linux32, linux64, osx-10-10, windows10-64 and windows7-32 all debug builds.
Recent failure log: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=242716950&repo=mozilla-inbound&lineNumber=7704
Comment 5•6 years ago
|
||
I looked at the recent failure log from comment 4, and it is happening in the directory remote/test/browser/, so I think the recent spike in failures is more likely to be the leakcheck variant of bug 1547303, which also started on 4/24.
Comment 6•6 years ago
|
||
I looked at about 1 out of 10 of the failure logs from comment 4, and I'd say 90% or more of them are in remote/test/browser/. There were also a couple of failures in service worker related tests, but it didn't seem that bad.
Comment hidden (Intermittent Failures Robot) |
Comment 8•6 years ago
|
||
We disabled remote/test/browser/browser_cdp.js because it perma-failed
the leakcheck in bug 1546945 and we thought it was limited to that
test specifically. According to this and bug 1547303, it appears
to happen also for the other tests in the same directory, though
less frequently.
We should disable all the browser-chrome tests under remote/test/browser/
until we’ve had time to plug the leak.
Comment hidden (Intermittent Failures Robot) |
Assignee | ||
Updated•4 years ago
|
Updated•3 years ago
|
Description
•