Leak of window created during docshell/test/browser/browser_alternate_fixup_middle_click_link.js
Categories
(Core :: DOM: Navigation, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox123 | --- | fixed |
People
(Reporter: mccr8, Assigned: emilio)
References
(Blocks 1 open bug)
Details
Attachments
(1 file, 1 obsolete file)
|
Bug 1866884 - Make browser_alternate_fixup_middle_click_link.js wait for error page properly. r=Gijs
48 bytes,
text/x-phabricator-request
|
Details | Review |
This leak has shown up twice in bug 1866073, and I think I've seen leaks before while running this docshell directory so maybe it is the same thing. I'm not sure what the cause is.
| Reporter | ||
Comment 1•2 years ago
|
||
It looks like this test intentionally loads an about:neterror page, so maybe this is another instance of the shutdown issue Emilio worked around for a few tests in bug 1865771.
Updated•2 years ago
|
| Reporter | ||
Comment 2•1 year ago
|
||
Emilio, any ideas how we could stop this testing leak? Like maybe the test could explicitly wait until Stylo has finished dealing with about:neterror somehow? It seems to be one of the more frequent leaks. Unfortunately unlike bug 1865771 this test is intentionally loading a page that causes about:neterror so we can't fix it to a valid URL. Thanks.
| Assignee | ||
Comment 3•1 year ago
|
||
Not sure if we can wait for the load event of about:neterror somehow. Nika, do you happen to know?
Comment 4•1 year ago
|
||
(In reply to Emilio Cobos Álvarez (:emilio) from comment #3)
Not sure if we can wait for the load event of about:neterror somehow. Nika, do you happen to know?
There's a waitForErrorPage helper on BTU right? https://searchfox.org/mozilla-central/rev/f465027ef4d334dbc9ad270718c8a5e8045e7a2b/testing/mochitest/BrowserTestUtils/BrowserTestUtils.sys.mjs#1657
I think this is already being used in this test, cf. https://searchfox.org/mozilla-central/rev/f465027ef4d334dbc9ad270718c8a5e8045e7a2b/docshell/test/browser/browser_alternate_fixup_middle_click_link.js#26-39 - but not all the time. And I expect that when we hit the condition checked there (ie the currentURI has already updated), it may not have finished loading, and although that's sufficient for the test it's not sufficient to stop it leaking.
| Assignee | ||
Comment 5•1 year ago
|
||
While I'm looking at this / bug 1866884, this it probably makes sense,
wdyt?
Updated•1 year ago
|
| Assignee | ||
Updated•1 year ago
|
Comment 6•1 year ago
|
||
Comment on attachment 9372847 [details]
Bug 1866884 - Convert aboutNetError to an html page. r=Gijs
Revision D198571 was moved to bug 1874701. Setting attachment 9372847 [details] to obsolete.
| Assignee | ||
Comment 7•1 year ago
|
||
Depends on D198571
Comment 9•1 year ago
|
||
| bugherder | ||
| Reporter | ||
Comment 10•1 year ago
|
||
Thanks Emilio and Gijs for your work here! Hopefully this will help reduce the failure rate of these window leaks.
Description
•