CLOSED TREE
Backed out changeset a9e341a38fae (bug 1742582)
Backed out changeset a9ba4a859295 (bug 1742582)
Backed out changeset bd9307118864 (bug 1742582)
Use Extension:FlushJarCache listener in ExtensionProcessScript.jsm instead,
it's already loaded everywhere and early enough from AddonManager.jsm.
Differential Revision: https://phabricator.services.mozilla.com/D129952
Acording to crash reports, obsfucating the NSS DB locations did not help, so
this patch un-does the changes and un-migrates any migrated DB locations.
Differential Revision: https://phabricator.services.mozilla.com/D129323
This patch moves the addons-search-detection system add-on in tree and
adjusts the build configuration to make it a built-in add-on (which
requires changes in the `BrowserGlue.jsm` file).
Summary of the changes made to the different files:
- `api.js`: added license header, reformatted with Prettier, then fixed
ESLint errors: use of `Services.eTLD` instead of
`XPCOMUtils.defineLazyServiceGetter(...)` and defined
`"searchInitialized"` on `this` instead of `global` which was unknown
- `background.js`: added license header, reformatted with Prettier,
removed debug logs because they were off by default anyway, fixed
ESLint error: id => addonId because addonId was already defined in a
parent scope
- `manifest.json`: version number changed + `hidden: true`
- `schema.json`: no change await addon.enable();
Depends on D129019
Differential Revision: https://phabricator.services.mozilla.com/D128908
Some crash reports appear to be indicating that initializing NSS' certificate
and key databases is taking on the order of minutes in some cases, which is
unexpected. One hypothesis is that third-party software is opening these DBs at
the same time that NSS is operating on them, causing contention and thus
slowness. This patch experimentally (in Nightly only) renames these DBs in the
hopes that third-party software might not recognize them as the DBs it's
looking for, and will thus leave them alone.
Differential Revision: https://phabricator.services.mozilla.com/D126028
Some crash reports appear to be indicating that initializing NSS' certificate
and key databases is taking on the order of minutes in some cases, which is
unexpected. One hypothesis is that third-party software is opening these DBs at
the same time that NSS is operating on them, causing contention and thus
slowness. This patch experimentally (in Nightly only) renames these DBs in the
hopes that third-party software might not recognize them as the DBs it's
looking for, and will thus leave them alone.
Differential Revision: https://phabricator.services.mozilla.com/D126028
Depends on D126371
Now that the MarionetteEvents actors remain registered, MarionetteEventsChild.jsm and its Log.jsm dependencies both show up in the test browser_startup_content.js
Differential Revision: https://phabricator.services.mozilla.com/D126519
Some crash reports appear to be indicating that initializing NSS' certificate
and key databases is taking on the order of minutes in some cases, which is
unexpected. One hypothesis is that third-party software is opening these DBs at
the same time that NSS is operating on them, causing contention and thus
slowness. This patch experimentally (in Nightly only) renames these DBs in the
hopes that third-party software might not recognize them as the DBs it's
looking for, and will thus leave them alone.
Differential Revision: https://phabricator.services.mozilla.com/D126028
Depends on D126371
Now that the MarionetteEvents actors remain registered, MarionetteEventsChild.jsm and its Log.jsm dependencies both show up in the test browser_startup_content.js
Differential Revision: https://phabricator.services.mozilla.com/D126519
Some crash reports appear to be indicating that initializing NSS' certificate
and key databases is taking on the order of minutes in some cases, which is
unexpected. One hypothesis is that third-party software is opening these DBs at
the same time that NSS is operating on them, causing contention and thus
slowness. This patch experimentally (in Nightly only) renames these DBs in the
hopes that third-party software might not recognize them as the DBs it's
looking for, and will thus leave them alone.
Differential Revision: https://phabricator.services.mozilla.com/D126028
Previously, content processes would try to contact the X server
directly during startup to read color calibration information; with
`dom.ipc.avoid-gtk` this doesn't work because the process is in headless
mode. This patch extends the color profile IPC facility added in bug
1540776 for Windows sandboxing (win32k lockdown) to GTK under X11.
(Currently there's no support for color management under Wayland, so
there's nothing for this patch to fix in that case.)
Differential Revision: https://phabricator.services.mozilla.com/D124507
MOZ_WEBRENDER=0 now does nothing -- you will either get HW-WR or SW-WR
depending on the platform configuration. The pref
gfx.webrender.force-legacy-layers is removed. This leaves no
configuration option to disable WebRender.
MOZ_WEBRENDER=1 will continue to force WR on, which will ensure in CI we
get HW-WR unless gfx.webrender.software is true.
Differential Revision: https://phabricator.services.mozilla.com/D122474
The URLQueryStrippingListService will get initialized too late in
Fission because the 'profile-after-change' won't be triggered for
content processes in Fission. So, it won't have a complete list when the
query stripping happens because it will be initalized by then.
To address this issue, we add a content process script which will run
during the creation of content processes and it will get the service to
initialize it early so that we will have a complete list when doing the
stripping.
Differential Revision: https://phabricator.services.mozilla.com/D117376
