936c5d6bd40b08188993cbd08e8622820398687a: Merge inbound to mozilla-central a=merge
arthur.iakab <aiakab@mozilla.com> - Tue, 07 Aug 2018 18:42:40 +0300 - rev 485443
Push 9719 by ffxbld-merge at Fri, 24 Aug 2018 17:49:46 +0000
Merge inbound to mozilla-central a=merge
7791fe11b664cf5a1a19e99b32c92e228d8d0c27: Bug 1481229 part 2 - Always use the unwrapped object in Logging::formatObject. r=evilpie
Jan de Mooij <jdemooij@mozilla.com> - Tue, 07 Aug 2018 14:06:45 +0200 - rev 485442
Push 9719 by ffxbld-merge at Fri, 24 Aug 2018 17:49:46 +0000
Bug 1481229 part 2 - Always use the unwrapped object in Logging::formatObject. r=evilpie
de88f2fd6d4d8895a8c3d174e630fbec58e628d1: Bug 1481229 part 1 - Remove unnecessary realm entering in JavaScriptShared::findObjectById. r=evilpie
Jan de Mooij <jdemooij@mozilla.com> - Tue, 07 Aug 2018 14:06:45 +0200 - rev 485441
Push 9719 by ffxbld-merge at Fri, 24 Aug 2018 17:49:46 +0000
Bug 1481229 part 1 - Remove unnecessary realm entering in JavaScriptShared::findObjectById. r=evilpie ToWindowProxyIfWindow does not rely on the current realm in any way.
f865653db6dc62c8d1eee995966dcdcff40ac0bb: Bug 1480678 part 9 - Assert IDBWrapperCache::mScriptOwner is a global and use JSAutoRealm instead of JSAutoRealmAllowCCW. r=mrbkap
Jan de Mooij <jdemooij@mozilla.com> - Tue, 07 Aug 2018 14:06:45 +0200 - rev 485440
Push 9719 by ffxbld-merge at Fri, 24 Aug 2018 17:49:46 +0000
Bug 1480678 part 9 - Assert IDBWrapperCache::mScriptOwner is a global and use JSAutoRealm instead of JSAutoRealmAllowCCW. r=mrbkap
883d78be26bf84bc3fc7ff6ccc44c49b9601f071: Bug 1480678 part 8 - Use JSAutoRealm instead of JSAutoRealmAllowCCW in nsObjectLoadingContent::SetupProtoChain. r=mrbkap
Jan de Mooij <jdemooij@mozilla.com> - Tue, 07 Aug 2018 14:06:45 +0200 - rev 485439
Push 9719 by ffxbld-merge at Fri, 24 Aug 2018 17:49:46 +0000
Bug 1480678 part 8 - Use JSAutoRealm instead of JSAutoRealmAllowCCW in nsObjectLoadingContent::SetupProtoChain. r=mrbkap I audited the callers and this function already does GetDOMClass(aObject)->mGetProto(aCx) elsewhere.
3f30b1a694972d96332c9165a6131cf400c68b44: Bug 1480678 part 7 - Use CallbackObject's callback global for realm entering in more places. r=bz
Jan de Mooij <jdemooij@mozilla.com> - Tue, 07 Aug 2018 14:06:44 +0200 - rev 485438
Push 9719 by ffxbld-merge at Fri, 24 Aug 2018 17:49:46 +0000
Bug 1480678 part 7 - Use CallbackObject's callback global for realm entering in more places. r=bz
1efeecd0ac69a8f5852ee48e3a5539e3b3e367e4: Bug 1474900: Assert there are no pending locks when destroying the image proxy. r=tnikkel
Emilio Cobos Álvarez <emilio@crisal.io> - Wed, 11 Jul 2018 17:06:40 +0200 - rev 485437
Push 9719 by ffxbld-merge at Fri, 24 Aug 2018 17:49:46 +0000
Bug 1474900: Assert there are no pending locks when destroying the image proxy. r=tnikkel
ef7f43b981ef872b3faa3a8d62d8115d59df1cd2: Bug 1481378 - Simplify mozconfig.linux32. r=ted
Mike Hommey <mh+mozilla@glandium.org> - Tue, 07 Aug 2018 16:28:13 +0900 - rev 485436
Push 9719 by ffxbld-merge at Fri, 24 Aug 2018 17:49:46 +0000
Bug 1481378 - Simplify mozconfig.linux32. r=ted All CI builds for linux32 have been running on 64-bits hosts for a long while now, and there are no 32-bits hosts left. We can remove the special-casing that makes the linux32 builds behave differently depending on the bit-width of the host. Furthermore, configure has been able to deal with adding -m32 on its own, so we don't need to add it to $CC/$CXX manually anymore.
738e88d3b78eaa4d34cc5d16fc9d2e2b993e228e: Bug 1476846 - Reduce latency of applying async images of video r=nical
sotaro <sotaro.ikeda.g@gmail.com> - Tue, 07 Aug 2018 19:12:06 +0900 - rev 485435
Push 9719 by ffxbld-merge at Fri, 24 Aug 2018 17:49:46 +0000
Bug 1476846 - Reduce latency of applying async images of video r=nical
0e079d9d66419da1281eeb6b6cb148899cc90e0b: Bug 1478359 - Use nsXPCWrappedJS's object global as nonCCWObject in nsFrameMessageManager::ReceiveMessage. r=bz
Jan de Mooij <jdemooij@mozilla.com> - Tue, 07 Aug 2018 11:57:51 +0200 - rev 485434
Push 9719 by ffxbld-merge at Fri, 24 Aug 2018 17:49:46 +0000
Bug 1478359 - Use nsXPCWrappedJS's object global as nonCCWObject in nsFrameMessageManager::ReceiveMessage. r=bz
b3c093b141e2381efef699124f8a629d0711c8c6: Bug 1478359 - Store a global object in nsXPCWrappedJS and use it for realm-entering. r=mccr8
Jan de Mooij <jdemooij@mozilla.com> - Tue, 07 Aug 2018 11:57:41 +0200 - rev 485433
Push 9719 by ffxbld-merge at Fri, 24 Aug 2018 17:49:46 +0000
Bug 1478359 - Store a global object in nsXPCWrappedJS and use it for realm-entering. r=mccr8 The problem we're solving here: getting/entering the realm/global of a cross-compartment wrapper doesn't make sense once there are multiple realms in a compartment and the CCW will be shared by all of them. Because nsXPCWrappedJS can store a CCW, we will no longer be able to use this JSObject to enter the target realm. What this patch does: we pass a JSContext* to nsXPCWrappedJS::GetNewOrUsed and we use this to store a global object in nsXPCWrappedJS (with the invariant that the object and global stored in nsXPCWrappedJS are same-compartment). Then when we want to enter the nsXPCWrappedJS's target realm, we use this global object instead of the maybe-CCW object. Because we currently still have one realm per compartment and the objects are same-compartment, this is guaranteed to preserve behavior for now. nsXPCWrappedJS has some code to deal with weak pointers. Fortunately this applies only to root wrappers and root wrappers always store an unwrapped JSObject, so the extra global we store is guaranteed to be marked by the GC in that case (a global object is never collected when there are live JSObjects belonging to the same realm).
bf6961db9405d45709a6a8be29212983160c0b26: Merge mozilla-central to inbound
arthur.iakab <aiakab@mozilla.com> - Tue, 07 Aug 2018 12:41:15 +0300 - rev 485432
Push 9719 by ffxbld-merge at Fri, 24 Aug 2018 17:49:46 +0000
Merge mozilla-central to inbound
ed655b5136856c68f73d87e49a685c7a1b9c4fd1: Bug 1478713 - Add some tests for the Wasm JS API; r=luke+bbouvier
Ms2ger <Ms2ger@igalia.com> - Tue, 07 Aug 2018 10:18:34 +0200 - rev 485431
Push 9719 by ffxbld-merge at Fri, 24 Aug 2018 17:49:46 +0000
Bug 1478713 - Add some tests for the Wasm JS API; r=luke+bbouvier
dbd2bfad3d7af86d83d67baef2105ae04186c51b: Bug 1480454 - Part e: Stop running disabled wpt tests in jstests; r=jgraham
Ms2ger <Ms2ger@igalia.com> - Tue, 07 Aug 2018 10:18:31 +0200 - rev 485430
Push 9719 by ffxbld-merge at Fri, 24 Aug 2018 17:49:46 +0000
Bug 1480454 - Part e: Stop running disabled wpt tests in jstests; r=jgraham
6b60feef3ce696cf3b00d89f520a7da67a7e2b1b: Bug 1480454 - Part d: Don't run wpt jstests in the jsreftest harness; r=bbouvier
Ms2ger <Ms2ger@igalia.com> - Tue, 07 Aug 2018 10:18:31 +0200 - rev 485429
Push 9719 by ffxbld-merge at Fri, 24 Aug 2018 17:49:46 +0000
Bug 1480454 - Part d: Don't run wpt jstests in the jsreftest harness; r=bbouvier These tests already run in the browser within the wpt setup.
3c2e6da29d5f30ac2a5edb824be56a6df0795c36: Bug 1480454 - Part c: Give RefTestCase a useful __repr__ implementation; r=bbouvier
Ms2ger <Ms2ger@igalia.com> - Tue, 07 Aug 2018 10:18:31 +0200 - rev 485428
Push 9719 by ffxbld-merge at Fri, 24 Aug 2018 17:49:46 +0000
Bug 1480454 - Part c: Give RefTestCase a useful __repr__ implementation; r=bbouvier
a0ed2387d4a4e4e9da1cc5b1c934765cc974c297: Bug 1480454 - Part b: Improve assertion in _emit_manifest_at; r=bbouvier
Ms2ger <Ms2ger@igalia.com> - Tue, 07 Aug 2018 10:18:31 +0200 - rev 485427
Push 9719 by ffxbld-merge at Fri, 24 Aug 2018 17:49:46 +0000
Bug 1480454 - Part b: Improve assertion in _emit_manifest_at; r=bbouvier This adds a message to the assertion, and removes a leftover pdb invocation (which causes unnecessary delays if it is triggered in automation).
009f3d9799b6000f414462501550863b87e5ae1b: Bug 1480454 - Part a: Add a wasm setting to the wpt .ini expectation files; r=jgraham
Ms2ger <Ms2ger@igalia.com> - Tue, 07 Aug 2018 10:18:31 +0200 - rev 485426
Push 9719 by ffxbld-merge at Fri, 24 Aug 2018 17:49:46 +0000
Bug 1480454 - Part a: Add a wasm setting to the wpt .ini expectation files; r=jgraham
09cd991472c91745e9e14da56b7f7d227cc3c073: Bug 1481138 - Clarify that Hash{Map,Set}::putNew() can be used if elements have been removed. r=luke
Nicholas Nethercote <nnethercote@mozilla.com> - Mon, 06 Aug 2018 12:01:28 +1000 - rev 485425
Push 9719 by ffxbld-merge at Fri, 24 Aug 2018 17:49:46 +0000
Bug 1481138 - Clarify that Hash{Map,Set}::putNew() can be used if elements have been removed. r=luke Hash{Map,Set}::putNew() can be used on a table that has had elements removed, despite some comments to the contrary. This patch fixes those comments. It also clarifies when putNewInfallible() can be used. This patch also removes the !isRemoved() assertion in findFreeEntry(), which is confusing -- !isLive() would be more precise, but also obvious from the surrounding code. MozReview-Commit-ID: q4qwKGBsHx
01dcd8f80341ec39c949e364d5f46fd9c97963da: Bug 1481138 - Remove HashMap::lookupWithDefault(). r=luke
Nicholas Nethercote <nnethercote@mozilla.com> - Mon, 06 Aug 2018 09:45:38 +1000 - rev 485424
Push 9719 by ffxbld-merge at Fri, 24 Aug 2018 17:49:46 +0000
Bug 1481138 - Remove HashMap::lookupWithDefault(). r=luke Because it's quite strange, badly named, not that useful, and barely used. Also remove WeakMap::lookupWithDefault(), which is similar, but not used at all. MozReview-Commit-ID: IhIl4hQ73U1
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip