Bug 1270108 - IonMonkey: Only keep a certain amount of IonBuilder waiting to get linked alive, r=jandem

Bug 1269462 - fix race condition in TabsInTitlebar code where it was possible we'd only be called before init(), resulting in never updating the titlebar maths, r=MattN,mconley

MozReview-Commit-ID: KM274gGpiuR

--HG--
extra : rebase_source : 06cfc19ce026cfc033fff0a6b0c6a455c78e0cdf

MozReview-Commit-ID: 95bQjH6FNnD

--HG--
extra : rebase_source : 0e7039ccb7d02636effdf1850ea162335a979734

DONTBUILD (NPOTB)

MozReview-Commit-ID: Hqk3kSUftRM

--HG--
extra : rebase_source : c193442d7018355914f731d94dba587e480443bf

Bug 1111440 - Replace rest of -moz-/Moz prefixed logical margin/padding/border properties with their standard versions.  r=heycam

This patch was generated by the command:
  find * -type f -exec sed -i -f ../mozpropsub {} \;
in the root of the repository, with the file ../mozpropsub containing:
s/-moz-padding-end\>/padding-inline-end/g
s/-moz-padding-start\>/padding-inline-start/g
s/-moz-margin-end\>/margin-inline-end/g
s/-moz-margin-start\>/margin-inline-start/g
s/-moz-border-end\>/border-inline-end/g
s/-moz-border-end-color\>/border-inline-end-color/g
s/-moz-border-end-style\>/border-inline-end-style/g
s/-moz-border-end-width\>/border-inline-end-width/g
s/-moz-border-start\>/border-inline-start/g
s/-moz-border-start-color\>/border-inline-start-color/g
s/-moz-border-start-style\>/border-inline-start-style/g
s/-moz-border-start-width\>/border-inline-start-width/g
s/\<MozPaddingEnd\>/paddingInlineEnd/g
s/\<MozPaddingStart\>/paddingInlineStart/g
s/\<MozMarginEnd\>/marginInlineEnd/g
s/\<MozMarginStart\>/marginInlineStart/g
s/\<MozBorderEnd\>/borderInlineEnd/g
s/\<MozBorderEndColor\>/borderInlineEndColor/g
s/\<MozBorderEndStyle\>/borderInlineEndStyle/g
s/\<MozBorderEndWidth\>/borderInlineEndWidth/g
s/\<MozBorderStart\>/borderInlineStart/g
s/\<MozBorderStartColor\>/borderInlineStartColor/g
s/\<MozBorderStartStyle\>/borderInlineStartStyle/g
s/\<MozBorderStartWidth\>/borderInlineStartWidth/g

The diffs for the following files:
  layout/style/nsCSSPropAliasList.h
  layout/style/test/property_database.js
  layout/style/test/test_value_computation.html
were then manually removed from the patch.

MozReview-Commit-ID: 8fbYnlZcn9U

The decoding loop in Decoder::Decode only pauses to report progress when it runs out of bytes to decode. So for long animated images where the network is keeping up with decoding it will be a relatively long time until we deliver the first frame complete notification and corresponding invalidation. In most cases this shouldn't be too expensive as it is just dispatching a runnable to the main thread from the decoding thread.

Bug 1272757 - Fix drag handling so that drag inputs don't get stuck waiting for content response while running tests. r=rbarker

MozReview-Commit-ID: Lsn5nFNcP7k

MozReview-Commit-ID: 7A7GuatX98k

MozReview-Commit-ID: EhHLaIy9lyq

MozReview-Commit-ID: GBsEOnuO224

Bug 1272160.  Fix XPCWrappedNativeScope::AddSizeOfIncludingThis to not blindly poke at non-DOM globals as if they were DOM globals.  r=khuey

I did audit the XPConnect callers of TraceProtoAndIfaceCache and DestroyProtoAndIfaceCache, and they all check JSCLASS_DOM_GLOBAL.

Bug 1270783.  If we end up erroring out of a worker main-script load before we get to creating a global for the worker, don't try to enter that global's compartment to throw an exception.  Just squelch it instead.  r=khuey

Previously, we took an IntRect converted to Rect and then later wanted
ints in the backend. This avoids all of that.

This will ensure that the GC zeal argument won't get truncated needlessly.

This affects both the environment variable JS_GC_ZEAL, and the --gc-zeal
argument to the JS shell.

Previously, we took an IntRect converted to Rect and then later wanted
ints in the backend. This avoids all of that.

Backed out changeset 2ac62de7365d (bug 1271002) for crash in GTest: [@ mozilla::image::RasterImage::UpdateImageContainer]. r=backout

MozReview-Commit-ID: 6XxWnWGkiZn

--HG--
extra : rebase_source : 8e7062c10c071ce7ad7a8319101961db8da6eabd

So we can release the bug fixes we just made.

MozReview-Commit-ID: HgfPQkkwd6r

--HG--
extra : rebase_source : 62a85de968b26230721939838ca4d29d6600b186

I believe this is the source of hangs/timeouts in automation.
join() waits forever. We add code to wait at most N seconds before
force terminating the process. The timeout is a bit high. But it is
better than infinite.

MozReview-Commit-ID: KwyO4RZ9OqL

--HG--
extra : rebase_source : 767d8ff5b48d7e75ab8fe72b18145446a38d439a

Before, we kept waiting for data in the pipe after receiving the
"done" message. This didn't really make much sense because the
"done" message should be the final thing sent over the pipe!

e9113fd6cdb8 (bug 1239939) recently dropped the poll interval
of the pipe from 1.0 to 0.1s. This appears to have introduced
an intermittent failure in a test. The race condition was
between the child process sending data and the parent process
timing out (after only 0.1s) waiting for that data. Increasing
the timeout makes the failure reproduce less often. Although
technically the race condition is still present! I'm not
inclined to fix it at this time, however.

The rationale for dropping the pipe timeout was that it was
causing lag when terminating short-lived processes. Now that
we abort the pipe reading/polling loop as soon as the "done"
message is received, we no longer poll the pipe after receiving
"done" and no longer have to worry about its timeout impacting
shutdown time.

MozReview-Commit-ID: EeENQ95RAs1

--HG--
extra : rebase_source : ce2502f32841a55f912aafdba7cc81e3a58e3ff5

Found this bug when auditing the code for issues. We are attempting
to send a tuple but were forgetting the trailing comma on a single
element tuple.

Fortunately, this doesn't appear to impact anything because
the receiving end of the pipe doesn't care what data it receives.

MozReview-Commit-ID: E34fBqxgUSq

--HG--
extra : rebase_source : 3701a28979a8b53d40ea68acef3ee2cb6d8a50f2

Bug 1272269: IonMonkey - Reintroduce template object on the VM variant of MNewArray And MNewObject, r=efaust

Bug 1259345: Let layout.css.prefixes.webkit ride the trains (and be default-enabled even in release builds). r=cjku

MozReview-Commit-ID: KNe9DdICX0Y