зеркало из https://github.com/mozilla/gecko-dev.git
d755ee2dc7
The way this test works is, it loads a page, then it navigates to another page and exits. The mochitest browser-chrome leak detector will report a leak if the first page isn't freed by the end of the test. To make this Fission-compatible, I first changed the page we navigate to to be same-origin. This means that we won't tear down the original process immediately when we navigate, which will break the various test harness stuff. Secondly, I enable the dom.ipc.keepProcessesAlive.webIsolated preference, which means that the content process won't be torn down immediately. If this pref is not set, then the usual process reuse ends up destroying the window before the test ends, whether or not it leaks. I verified that this test fails when the patch from bug 1336811 is backed out, both with and without Fission. Differential Revision: https://phabricator.services.mozilla.com/D51944 --HG-- extra : moz-landing-system : lando |
||
|---|---|---|
| .. | ||
| tests | ||
| XMLHttpRequest.cpp | ||
| XMLHttpRequest.h | ||
| XMLHttpRequestEventTarget.cpp | ||
| XMLHttpRequestEventTarget.h | ||
| XMLHttpRequestMainThread.cpp | ||
| XMLHttpRequestMainThread.h | ||
| XMLHttpRequestString.cpp | ||
| XMLHttpRequestString.h | ||
| XMLHttpRequestUpload.cpp | ||
| XMLHttpRequestUpload.h | ||
| XMLHttpRequestWorker.cpp | ||
| XMLHttpRequestWorker.h | ||
| moz.build | ||