Target.setDiscoverTargets should only emit targetCreated events when ran
with discover as true. Also added tests for discover false.
Differential Revision: https://phabricator.services.mozilla.com/D167210
Benchmark results show that using parallel marking is not always a win for
small heaps, so add a threshold for its use.
This is set to 10MB, which will result in using parallel marking ~70% of the
time.
This parameter is set to zero for jit-tests and shell js tests so we get test
coverage where heap sizes are expected to be small (and maximum performance is
not a goal).
Differential Revision: https://phabricator.services.mozilla.com/D175249
This patch introduces a way to put the main thread of background content processes in the background on MacOS. Currently disabled by default, and enabling for testing further restricts it to nightly only.
Differential Revision: https://phabricator.services.mozilla.com/D167952
Not sure if this is worth it, your call. But I wrote this so I figured
someone debugging this code might find it useful.
Depends on D172033
Differential Revision: https://phabricator.services.mozilla.com/D172034
This patch lays a foundation for running chromium-as-release binaries with our raptor-browsertime tests.
To start with, this just deals with the Linux platform and minimal changes will be required in patches in the near future for Win/MacOS platforms.
To begin with, we only test on priority benchmarks at the moment (e.g. sp/sp3).
Differential Revision: https://phabricator.services.mozilla.com/D173757
This patch adds a Dockerfile and shell script for building an official custom configuration of Chromium i.e. "chromium-as-release" (CaR).
These CaR builds will be much more useful and realistic than our existing chromium performance tests in CI when doing
browser-browser comparisons for benchmarks, page load tests, etc.
Differential Revision: https://phabricator.services.mozilla.com/D173756
These objects are either internal JS Object created internally within spidermonkey,
or some objects that the Debugger API wasn't able to retrieve a precise allocation stack.
In both cases, it makes the investigations hard as we have no clue what these objects are.
Differential Revision: https://phabricator.services.mozilla.com/D175347
Reserve the lower positions of the file descriptors to make sure
we don't reuse stdin/stdout/stderr in case they we closed
before launch.
Differential Revision: https://phabricator.services.mozilla.com/D175337
Repeating D169484 before merging those classes.
(Skipping AsyncWait cancellation as per Nika streams should not reject resubscription. I'll fix it separately.)
Differential Revision: https://phabricator.services.mozilla.com/D174764
In Nightly, we enable FEATURE_HARDWARE_VIDEO_DECODING by default. Change FEATURE_BLOCKED_PLATFORM_TEST VA-API test failure to FEATURE_BLOCKED_DRIVER_VERSION
fail as we support VA-API now but only on new Mesa.
In Beta/Release, we disable FEATURE_HARDWARE_VIDEO_DECODING by default. Change FEATURE_BLOCKED_PLATFORM_TEST VA-API test failure to
FEATURE_BLOCKED_DEVICE/FEATURE_HARDWARE_VIDEO_DECODING_DISABLE to match nsGfxInfo rule.
Differential Revision: https://phabricator.services.mozilla.com/D175236
glxtest is run later when Firefox already spawns threads. Recently glxtest runs in forked process
which doesn't work correctly in multi-thread environment, so we need to move glxtest to different binary file
and launch it as stand alone code.
Differential Revision: https://phabricator.services.mozilla.com/D173486
- Implement fire_vaapi_process() which launch VA-API test utility on given DRM device.
- Implement GfxInfo::GetDataVAAPI() which gets VA-API test results
- Run VA-API tests when FEATURE_HARDWARE_VIDEO_DECODING is probed and only if it's enabled by GfxInfo.
Differential Revision: https://phabricator.services.mozilla.com/D171995
Right now we fire glxtest on every Firefox start, even if we going to update, restart or ping running remote instance.
When we're running on system with broken/unstable gfx drivers (drivers/glx freezes or crashes) every such action is delayed or coredumps are generated on systems.
In this patch we launch glx test proces later if we know we need it.
Depends on D168650
Differential Revision: https://phabricator.services.mozilla.com/D168651