"alloc-failure" is completely unused apart from the description text in nsI-
Memory.idl (and has been since before Firefox 17), while "lowering-priority" is
still being checked for in the PuppetWidget, but otherwise unused as well since
the feature using it was decommissioned in bug 1234176.
Since we're touching the PuppetWidget code anyway, we take the opportunity to
add a check for "low-memory-ongoing" instead, since similar as to how things
used to be with "lowering-priority", we want to drop the LayerManager's cached
resources only when receiving a real full memory-pressure event, but not for
subsequent ongoing notifications.
MozReview-Commit-ID: HL03SOU8axe
--HG--
extra : rebase_source : c988769df36d8d77f4770c71d5c5e0d75c3b99af
For some reason, the CC spends a lot of time tracing jsids on
ObjectGroups when an addon is installed. This patch avoids that by
adding a canSkipJsids flag to JSTracer, and using it in
ObjectGroup::traceChildren. If this is true, then the tracer is free
to not report every jsid. This flag is set to true for the two CC
tracers.
MozReview-Commit-ID: CWFqQEr0SxV
--HG--
extra : rebase_source : cc31c22717f8990166454db191e0d40c145e09f0
Replaces:
- Metamarket on desktop (meta.ua)
- Yandex Market on mobile (market.yandex.ua)
MozReview-Commit-ID: DDhF7ppZtV8
--HG--
extra : rebase_source : a9bd18a40b9262bda1c570969ac3ee808b5dd776
Mainly so searching "toolchain" + "gcc" yields something useful in the
taskgraph.
MozReview-Commit-ID: HWiT3AwwYQ2
--HG--
extra : rebase_source : b1ba0dfb4f99b6f8abe42506e8b37db68ed03590
This patch enables differencing test coverage reports with baseline reports so that test reports contain what is unique to the test and excludes what is common to all tests (based on test file types: html, xul, js).
MozReview-Commit-ID: LHzlFZ72Ufi
--HG--
extra : rebase_source : ef4e0b5505cc85e95e1717d056d38c00d78872c5
The tests added in this patch will be used as a baseline for coverage that is common to all tests. They are added to each chunk being run in the test-coverage suite only if a test with an associated baseline type exists.
MozReview-Commit-ID: 1CrRZ1Ev2Mz
--HG--
extra : rebase_source : e2e4f9a51c82c637c8892dd8a5dbd84704b67b54
This also fixes all the tests to not rely on eval() anymore.
MozReview-Commit-ID: 8H8r497nQVK
--HG--
extra : rebase_source : 89c7f8a6e1bb77ceb242f05749c22d929ee86929
During session initialization, pass in the enabled state of all modules
through the init-data, and use that to enable modules if necessary. This
avoids a race condition where we enable modules too late on startup due
to event queuing.
MozReview-Commit-ID: I0rvq6UoOVh
--HG--
extra : rebase_source : df5d469d0b4a0a402e4b75cd74e52559f395e6bc
There's a race in EventDispatcher, where the ready state can change
during a dispatch. In that case, we can end up neither dispatching an
event nor queuing it, which effectively drops the event.
MozReview-Commit-ID: GvjSUzjBrsT
--HG--
extra : rebase_source : bed4e368b5ab1cc7653daea57f20ab25dfa1f125
From the main thread, we need to get the result of evaluateJS()
asynchronously, because the JS code may depend on delegate callbacks on
the main thread, which cannot happen if evaluateJS() is synchronous. The
simplest example is an alert() JS call that depends on the prompt
delegate callback.
This patch makes RDPConnection read input packets on a background
thread, and the main thread can either poll for input synchronously, or
rely on asynchronously posted messages. Actor is extended to allow for
multiple pending inputs, and it now exposes a nicer ReplyParser
interface for turning reply packets into result objects.
MozReview-Commit-ID: I0eKeOzf2Jy
--HG--
extra : rebase_source : d12ad5f4c876f51e944ff202289cdc7e29b5bf99
As a workaround for bug 1411513, about Log.jsm not supporting E10s,
testing/marionette/listener.js makes a synchronous call (sendSyncMessage)
to the main process asking for the Marionette logger repository's level.
We can avoid this blocking operation by using initialProcessData,
which is new since the workaround was implemented.
initialProcessData is a dictionary structured clone serialisable
that gets copied to the content process when it starts. Because the
Marionette log level cannot be changed at runtime it should be fine
to only send this data once per child process.
MozReview-Commit-ID: 3czydqGZpZH
--HG--
extra : rebase_source : 1aaae676d2b56c609844238e8173b64d300e3e00
To represent the parent process, we use a ChromeActor/TabActor that
targets a random chrome window. However, if that chrome window later
closes, the ChromeActor will stop working. In that case, we should clear
the cached ChromeActor and create a new one that targets a different
chrome window.
MozReview-Commit-ID: AP8AXEXEgAl
--HG--
extra : rebase_source : 28ccf09c79f23baed5714de281a8dd56bf4ecb4d
Add GeckoSessionTestRule.setPrefsUntilTestEnd and
GeckoSessionTestRule.setPrefsDuringNextWait so tests can easily set
prefs to get specific behavior.
MozReview-Commit-ID: FquaonwfF5v
--HG--
extra : rebase_source : 8a9a543a89f0976ef8476630cd9192518c4a9cfc
Add GeckoSessionTestRule.evaluateChromeJS for JS code that requires
chrome privileges, such as setting prefs.
MozReview-Commit-ID: G7NUKukWTT8
--HG--
extra : rebase_source : c0d4684ba5a9d4735e30b49f584e8e0222210c87
This factors out the prefs that are common across raptor, talos and
mochitest/web-platform-tests. In order to do this a new "unittest" profile has
been created.
This means, to set a pref across everything that uses this system, edit:
testing/profiles/common/user.js
To set a pref across unittest frameworks (which excludes raptor and talos),
edit:
testing/profiles/unittest/user.js
Setting a pref for perf frameworks only remains the same. Extensions follow
the same rules (drop them in <profile>/extensions).
MozReview-Commit-ID: 6AHlYsN0Lb8
--HG--
extra : rebase_source : aad259f06af549f3bc707fed5b1caaacf25bc28f
Don't use MOZ_MAKE_ENUM_CLASS_BITWISE_OPERATORS; it's unneeded here right now,
and occludes "PSM::Result" on Windows.
--HG--
extra : transplant_source : %B9%24%7FR%A8%1B%B0%3B%D44%ED%C5%3F%CD%1E%96%1F%22m%A3
Per Bug 1437754 comment 10, the pref security.pki.distrust_ca_policy makes more
sense as a bitmask than a state. To permit future nuance, let's go ahead and do
that before people start implementing atop Bug 1456112.
This does permit both 0b10 and 0b11 to enable the functionality for Firefox 63.
--HG--
extra : transplant_source : %84%AF%89%E0%89dT%01%10%84%A0%3B%A5%28%2A%D3%E1%B0%0D%E7
The Fennec CrashReporter class is also renamed to
CrashReporterActivity. When running in Fennec, the Activity will be used
which retains what we do today, prompting for comments, email, etc. When
used in standalone GeckoView, we report the crash without user
interaction if the appropriate GeckoRuntimeSetting was set. The app will
want to ask for user permission at least once in order to set this.
We do not collect the URL, email, or logcat with GeckoView crashes.
Logcat and URL would be nice to have, but it's not clear what the API
for those would look like, and they can be addressed in followup
patches.
MozReview-Commit-ID: C5ROsUKreRe
Right now we pass a bundle to GeckoLoader.setupGeckoEnvironment() with
magic keys representing the environment variables. Instead of this,
simply pass a list of Strings.
MozReview-Commit-ID: D6mSTnYpnGu
Ed Lee
Jan Henning
k88hudson
Luca Greco
Andrew McCreight
Emilio Cobos Álvarez
Francesco Lodolo (:flod)
Kartikaya Gupta
Simon Fraser
Gregory Szorc
Gregory Mierzwinski
Nicholas Hurley
Panos Astithas
Gijs Kruitbosch
Jim Chen
Andreas Tolfsen
Xidorn Quan
Jonathan Kingston
Bogdan Tara
Margareta Eliza Balazs
Randell Jesup
Andrew Halberstadt
YUKI "Piro" Hiroshi
arthur.iakab
J.C. Jones
Luke Wagner
Ognjen Galic
Dorel Luca
James Willcox
Csoregi Natalia