This will allow use of the DirectComposition virtual surface API. If
it turns out that some pages recreate surfaces a lot due to opacity
changing, we can add some extra logic to avoid recreating surfaces
as often, and making use of per-tile opacity in some cases.
Differential Revision: https://phabricator.services.mozilla.com/D57592
--HG--
extra : moz-landing-system : lando
I did some cleanup while here: This now uses the callback's lParam
instead of a global, and does the enumeration of all windows only if
the foreground window doesn't already belong to this process (which
was proposed in bug 259816 comment 68 but didn't make it into the patch).
Differential Revision: https://phabricator.services.mozilla.com/D57922
--HG--
extra : moz-landing-system : lando
nsWindow::UpdateOpaqueRegion() is used from Main thread and it collides with
moz_container_get_wl_surface() where opaque region is used and which is called from Compositor thread.
As a fix don't set opaque region directly for mozcontainer but rather just use a flag to signalize
there's an update needed and calculare/set the opaque region at moz_container_get_wl_surface() or
moz_container_egl_window_set_size().
Differential Revision: https://phabricator.services.mozilla.com/D58840
--HG--
extra : moz-landing-system : lando
Some adb logs produce badly encoded characters, producing errors.
Since the log is just informative, and getting pulled after the work
is done, we can ignore these errors and just warn that the adb logs
could not be retrieved.
Differential Revision: https://phabricator.services.mozilla.com/D58801
--HG--
extra : moz-landing-system : lando
If the condprof client retries getting a condprof, it will
display the traceback of the failure. If the task succeeds eventually,
this failure will pollute the logs and confuse Treeherder if there's
another problem later on in the job.
Differential Revision: https://phabricator.services.mozilla.com/D58802
--HG--
extra : moz-landing-system : lando
SpecialPowers.spawn bounces tasks off SpecialPowersParent before sending them
to SpecialPowersChild, which means that any operations which are sent
immediately afterwards and take a more direct route (like zoom changes) will
get to the content process before the task starts running. In the case of
tasks which depending on registering a listener before said operations take
place, this is obviously a problem.
So this patch fixes those cases in this test to wait for the listeners to be
setup before continuing.
Differential Revision: https://phabricator.services.mozilla.com/D57870
--HG--
extra : moz-landing-system : lando
Changes:
Demote linux32-shippable/opt tasks to tier 2 on all repositories. Other linux32 jobs are defined but do not appear to run.
Limit the build of linux32-shippable/opt to `try`/`mozilla-central`.
Differential Revision: https://phabricator.services.mozilla.com/D58207
--HG--
extra : moz-landing-system : lando
The previous patch was incorrect since by my logic mGCIsRunning should already have been true in AssertInvalidWrappedJSNotInTable. This ends up being false in two situations 1) during shutdown when the finalization callback that sets it has been removed and 2) when called during compacting GC.
This patch fixes the situation by setting it explicitly while we're inside WeakPointerZonesCallback and restoring the original value when we leave.
Differential Revision: https://phabricator.services.mozilla.com/D58818
--HG--
extra : moz-landing-system : lando
Converts `browser.newtabpage.enabled` into a static pref. Removes their varcache pref declaration. `signon.management.page.enabled` in the same file will be removed instead (Bug 1606888) as it is no longer needed.
Differential Revision: https://phabricator.services.mozilla.com/D58559
--HG--
extra : moz-landing-system : lando
This looks like a large change, but it's really just moving stuff
around.
It takes the logic in WinCompositorWidget and duplicates it into
its only 2 subclasses: InProcessWinCompositorWidget and
CompositorWidgetParent.
This is because CompositorWidgetParent is about to change *a lot*, but
InProcessWinCompositorWidget will basically stay the same. This is an
easy way to verify that I don't accidently break
InProcessWinCompositorWidget.
Differential Revision: https://phabricator.services.mozilla.com/D57428
--HG--
extra : moz-landing-system : lando
This is a backport of improvements made while working on Bug 1597336 we can
apply right away on condprof to speed up test execution and get more logs when
something goes wrong
Differential Revision: https://phabricator.services.mozilla.com/D58748
--HG--
extra : moz-landing-system : lando
The idle-inhibit protocol allows idle wake locks on Wayland
without any of the supported D-Bus interfaces running.
Differential Revision: https://phabricator.services.mozilla.com/D49095
--HG--
extra : moz-landing-system : lando
Defer the allocation of Scopes by implementing ScopeCreationData and family.
The idea is that we do not reify a GC allocated scope until
JSScript::fullyInitFromEmitter (the goal being to eventually move that onto
main thread).
Differential Revision: https://phabricator.services.mozilla.com/D51912
--HG--
extra : moz-landing-system : lando
Changes:
Demote linux32-shippable/opt tasks to tier 2 on all repositories. Other linux32 jobs are defined but do not appear to run.
Limit the build of linux32-shippable/opt to `try`/`mozilla-central`.
Differential Revision: https://phabricator.services.mozilla.com/D58207
--HG--
extra : moz-landing-system : lando
Changes:
Exclude the `linux-ccov` platform from ubuntu1804 migration plans for the time being.
The `linux64-ccov` test platform originally ran the `common-tests` test set so change the `linux-common-tests` to refer to `common-tests`. This should restore all sets of tests to the `linux64-ccov` label.
Differential Revision: https://phabricator.services.mozilla.com/D58739
--HG--
extra : moz-landing-system : lando
Use the same jitCodeRaw fallback strategy that visitKnownCall does to handle
potential lazy clones. We also stop allowing natives to flow into the
no-args-check case to avoid needing to guard against them.
Depends on D58097
Differential Revision: https://phabricator.services.mozilla.com/D58098
--HG--
extra : moz-landing-system : lando
When IonMonkey uses the no-arg-check entry point, we may still see lazy
function clones. In this case the no-arg-check entry point is unavailable,
but we can still fallback to the standard jitCodeRaw. This patch factors this
fallback behaviour out of visitCallKnown.
The new version guards the warmUpData tag bits instead of loading the
function flags. This makes it compatible with removing the INTERPRETED_LAZY
flag. In the future, the fallback case will no longer be necesarry once
delazification reuses the same script and all function clones delazify at
same time as their canonical one does.
Depends on D58096
Differential Revision: https://phabricator.services.mozilla.com/D58097
--HG--
extra : moz-landing-system : lando
Group the jitCodeRaw handling so it becomes simpler. By changing the scratch
register used by switchToObjectRealm we can move it later in code.
Differential Revision: https://phabricator.services.mozilla.com/D58096
--HG--
extra : moz-landing-system : lando
