Whitespace triming was used by only one caller, so it deserves to live
outside. Additionally, this defines the method name more precisely.
Depends on D44347
Differential Revision: https://phabricator.services.mozilla.com/D44348
--HG--
extra : moz-landing-system : lando
All calls to `profiler_add_marker()` (outside of the profilers code) are
now replaced by either:
- `PROFILER_ADD_MARKER(name, categoryPair)`
- `PROFILER_ADD_MARKER_WITH_PAYLOAD(name, categoryPair, TypeOfMarkerPayload,
(payload, ..., arguments))`
This makes all calls consistent, and they won't need to prefix the category pair
with `JS::ProfilingCategoryPair::`.
Also it will make it easier to add (and later remove) internal-profiling
instrumentation (bug 1576550), and to replace heap-allocated payloads with
stack-allocated ones (bug 1576555).
Differential Revision: https://phabricator.services.mozilla.com/D43588
--HG--
extra : moz-landing-system : lando
And remove the NodeInfoChanged override that used to call it.
This is dead since we removed the old style system. Was used to force a reparse
on cross-style-back-end adoption.
Differential Revision: https://phabricator.services.mozilla.com/D44134
--HG--
extra : moz-landing-system : lando
Existing tests will fail when there are more than 1 pending frames when Drain()
is called. Repeatly calling it to ensure all frames will be collected.
Differential Revision: https://phabricator.services.mozilla.com/D43689
--HG--
extra : moz-landing-system : lando
Some existing functions that manipulates H.264 bitstream already cover
most of the efforts for converting Android encoder output. With some minor
changes, they can be called by the encoder to avoid code duplications.
Differential Revision: https://phabricator.services.mozilla.com/D43686
--HG--
extra : moz-landing-system : lando
Provides coverage for an issue fixed in 1573381. Note that while that bug
discusses big endian machines, the tests added will cover both the big and
little endian case of the bug. This is because we have test cases that make sure
both octets of 16 wide char are being correctly compared.
Differential Revision: https://phabricator.services.mozilla.com/D44054
--HG--
extra : moz-landing-system : lando
Provides coverage for an issue fixed in 1573381. Note that while that bug
discusses big endian machines, the tests added will cover both the big and
little endian case of the bug. This is because we have test cases that make sure
both octets of 16 wide char are being correctly compared.
Differential Revision: https://phabricator.services.mozilla.com/D44054
--HG--
extra : moz-landing-system : lando
Sometime we would encouter a file putting all its samples on the type1 NAL, so we have to check its slice type in order to know if it's a keyframe or not.
The slice type is defined in the ITU-T Rec H.264 table 7.3, and it could be found in the slice_header in table 7.3.3.
Differential Revision: https://phabricator.services.mozilla.com/D35572
--HG--
extra : moz-landing-system : lando
- Listen for observer topics in the parent-process when in parent intercept mode
- Remove an extra postMessage call (and the corresponding message handler)
Differential Revision: https://phabricator.services.mozilla.com/D44513
--HG--
extra : moz-landing-system : lando
These tests compute the origin of their parent, in order to pass in as
the target origin argument to postMessage. They do this with
SpecialPowers.wrap(parent.window.location); which does not work with
Fission enabled, because the parent is often in another process. Every
web page in this directory is only ever has a single origin as a
parent, so we can hard code it as an argument to the first call to the
postMsg() helper method.
Differential Revision: https://phabricator.services.mozilla.com/D43307
--HG--
extra : moz-landing-system : lando
This doesn't fix the underlying problem but makes RunNextCollectorTimer more aggressive in what it does. Testing shows this substantially reduces the max GC heap size while running these tests as well as vsize and RSS. Hopefully this will fix the problem with the tests failing while we work out a good solution for the underlying issue.
Differential Revision: https://phabricator.services.mozilla.com/D44378
--HG--
extra : moz-landing-system : lando
This class allows to encapsulate all the information required in order to create a new HttpChannel object following a redirect.
Differential Revision: https://phabricator.services.mozilla.com/D40959