- May 14, 2016
-
-
JW Wang authored
MozReview-Commit-ID: GBsEOnuO224
-
Boris Zbarsky authored
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.
-
Boris Zbarsky authored
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
-
- May 13, 2016
-
-
Jeff Muizelaar authored
Previously, we took an IntRect converted to Rect and then later wanted ints in the backend. This avoids all of that.
-
Ehsan Akhgari authored
This will ensure that the GC zeal argument won't get truncated needlessly.
-
Ehsan Akhgari authored
-
Ehsan Akhgari authored
This affects both the environment variable JS_GC_ZEAL, and the --gc-zeal argument to the JS shell.
-
Wes Kocher authored
-
Wes Kocher authored
-
Wes Kocher authored
-
Wes Kocher authored
-
Jeff Muizelaar authored
Previously, we took an IntRect converted to Rect and then later wanted ints in the backend. This avoids all of that.
-
Nick Fitzgerald authored
-
Sebastian Hengst authored
Backed out changeset 2ac62de7365d (bug 1271002) for crash in GTest: [@ mozilla::image::RasterImage::UpdateImageContainer]. r=backout
-
Gregory Szorc authored
MozReview-Commit-ID: 6XxWnWGkiZn --HG-- extra : rebase_source : 8e7062c10c071ce7ad7a8319101961db8da6eabd
-
Gregory Szorc authored
So we can release the bug fixes we just made. MozReview-Commit-ID: HgfPQkkwd6r --HG-- extra : rebase_source : 62a85de968b26230721939838ca4d29d6600b186
-
Gregory Szorc authored
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
-
Gregory Szorc authored
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
-
Gregory Szorc authored
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
-
Hannes Verschore authored
Bug 1272269: IonMonkey - Reintroduce template object on the VM variant of MNewArray And MNewObject, r=efaust
-
Ryan VanderMeulen authored
-
George Wright authored
-
Daniel Holbert authored
Bug 1259345: Let layout.css.prefixes.webkit ride the trains (and be default-enabled even in release builds). r=cjku MozReview-Commit-ID: KNe9DdICX0Y
-
Daniel Holbert authored
Bug 1264905: Let layout.css.background-clip-text.enabled ride the trains (and be default-enabled even in release builds). r=cjku MozReview-Commit-ID: 4wGrPop8LcK
-
Patrick Brosset authored
MozReview-Commit-ID: GKnRmlqIBxb --HG-- extra : rebase_source : 69109deafb0af8113a31832b604208817a224dbb
-
Patrick Brosset authored
Bug 1267015 - Don't access the test content process in browser_styleinspector_tooltip-multiple-background-images.js; r=bgrins MozReview-Commit-ID: H0kgsYzG2x0 --HG-- extra : rebase_source : 7c20c72999895ed29744b2e64166be56e0e42141
-
Brian Grinstead authored
MozReview-Commit-ID: Lcyq6uLEdfk
-
Patrick Brosset authored
MozReview-Commit-ID: BreSVf4bPf --HG-- extra : rebase_source : 5ff6e97ba85c5d3bcd14db42aba10e5ee0a469e9
-
Patrick Brosset authored
Bug 1260630 - Don't use a CPOW to get data from content in browser_computed_style-editor-link.js; r=bgrins MozReview-Commit-ID: Jtb6C247ltM --HG-- extra : rebase_source : e24879ef5fbb63de8c3d0f7b637eafd6a35083c5
-
Patrick Brosset authored
Bug 1260630 - Don't use a CPOW to change style in content in browser_computed_refresh-on-style-change_01.js; r=bgrins MozReview-Commit-ID: 5tRJTzQLl2V --HG-- extra : rebase_source : ef28bb5449af3661fb7d26c7186f634137d55afe
-
Brian Grinstead authored
MozReview-Commit-ID: HCr0MFoMTiQ
-
Brian Grinstead authored
Bug 1256833 - Fix eslint issues in devtools/client/webconsole/test/browser_webconsole_bug_589162_css_filter.js;r=pbro MozReview-Commit-ID: LRbG1muyjqr
-
Brian Grinstead authored
MozReview-Commit-ID: 4HrOKosYk5w
-
- May 11, 2016
-
-
Botond Ballo authored
Bug 1270902 - Ensure scroll handoff parents are specified in the layer trees used by APZ gtests. r=kats MozReview-Commit-ID: BxFheQ058y8 --HG-- extra : rebase_source : 6d686831ee1a09aabaf1e4f66d8976849900d198 extra : source : 85b2ecd2a2ece0bdcb2243595707f85fb18b34f7 extra : histedit_source : 8e77e1a4a4142bf5e94713326efae728cb4b836f
-
Botond Ballo authored
MozReview-Commit-ID: 8DlQzhsjUOO --HG-- extra : rebase_source : a33438beab9e3c8a30d3cfe0f1818962c8de641e extra : source : 18098473f63e1be323be489ef9d833f8b36ac1fd extra : histedit_source : 533bba53774e970a01ecdd8a0162e8804350a986
-
- May 13, 2016
-
-
Nick Fitzgerald authored
-
Timothy Nikkel authored
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.
-
Andrea Marchesini authored
-
- May 10, 2016
-
-
Gijs Kruitbosch authored
Bug 1270144 - fix message from timed out tests to indicate the following crash is caused by us terminating the browser process, r=ahal,RyanVM MozReview-Commit-ID: Hyr7xkZdbqc --HG-- extra : rebase_source : 013339bec54f1ecb0123fa1388dbb350258790df extra : amend_source : 26e6c904d7031e700560ca32057edba65ad1632d
-
- May 13, 2016
-
-
Gijs Kruitbosch authored
MozReview-Commit-ID: 2P31nyL2eGQ --HG-- extra : amend_source : 79c50b2f8de7f54418752ae21f8a273c1f2adf6d
-