d8d5e13766642e0559cb45c5d93dc7de3548798c: Bug 1426797 - Mark image-size.xul as random on Windows. a=test-only
Ryan VanderMeulen <ryanvm@gmail.com> - Wed, 10 Jan 2018 20:46:36 -0500 - rev 452975
Push 1648 by mtabara@mozilla.com at Thu, 01 Mar 2018 12:45:47 +0000
Bug 1426797 - Mark image-size.xul as random on Windows. a=test-only
a4e1e729857b87d51e7f3f47c1ac414fb6233036: Bug 1418999 - Update PipelineId to associate the latest ImageContainer. r=sotaro
vincentliu <vliu@mozilla.com> - Thu, 11 Jan 2018 09:45:02 +0800 - rev 452974
Push 1648 by mtabara@mozilla.com at Thu, 01 Mar 2018 12:45:47 +0000
Bug 1418999 - Update PipelineId to associate the latest ImageContainer. r=sotaro
24b4c8683fc4c8c8a43c73c08b11dd7f4c63947c: Backed out changeset 28f876e75d47 (bug 1417680)for failing GTest
arthur.iakab <aiakab@mozilla.com> - Thu, 11 Jan 2018 02:56:49 +0200 - rev 452973
Push 1648 by mtabara@mozilla.com at Thu, 01 Mar 2018 12:45:47 +0000
Backed out changeset 28f876e75d47 (bug 1417680)for failing GTest
21bae0a7483d0730773e080d415290849d8074cb: Bug 1426873 - Implement no-arg Shape::dump() to allow calling T->dump() in a templatized function, r=jonco
Steve Fink <sfink@mozilla.com> - Fri, 17 Nov 2017 13:56:20 -0800 - rev 452972
Push 1648 by mtabara@mozilla.com at Thu, 01 Mar 2018 12:45:47 +0000
Bug 1426873 - Implement no-arg Shape::dump() to allow calling T->dump() in a templatized function, r=jonco
df08482843f63c374c0e45adbefd7fa2b5663ab2: No bug. Print diagnostic info when unexpected CFG structure seen in isUnrootedType(). r=me
Steve Fink <sfink@mozilla.com> - Tue, 17 Oct 2017 15:24:37 -0700 - rev 452971
Push 1648 by mtabara@mozilla.com at Thu, 01 Mar 2018 12:45:47 +0000
No bug. Print diagnostic info when unexpected CFG structure seen in isUnrootedType(). r=me
aec2c9f028767d630dec065feb781edb7dcfdd1c: Bug 1428507 - Avoid non-inlinable GCCellPtr constructing during tracing, r=jonco
Steve Fink <sfink@mozilla.com> - Fri, 05 Jan 2018 16:50:39 -0800 - rev 452970
Push 1648 by mtabara@mozilla.com at Thu, 01 Mar 2018 12:45:47 +0000
Bug 1428507 - Avoid non-inlinable GCCellPtr constructing during tracing, r=jonco
6f9bad2ae1812ba6f1ee3f97ad4054840dd030f0: Backed out changeset f56ef640d6c0 (bug 1428453) for failing web platform tests on /_mozilla/wasm/select.wast.js r=backout on a CLOSED TREE
Dorel Luca <dluca@mozilla.com> - Thu, 11 Jan 2018 02:17:12 +0200 - rev 452969
Push 1648 by mtabara@mozilla.com at Thu, 01 Mar 2018 12:45:47 +0000
Backed out changeset f56ef640d6c0 (bug 1428453) for failing web platform tests on /_mozilla/wasm/select.wast.js r=backout on a CLOSED TREE
600bee353e155608a5832f7eb9d5e42987d66591: Backed out 2 changesets (bug 1426783, bug 1425612) for spidermonekey bustages on non262/extensions/sharedtypedarray.js r=backout on a CLOSED TREE
Dorel Luca <dluca@mozilla.com> - Thu, 11 Jan 2018 01:45:10 +0200 - rev 452968
Push 1648 by mtabara@mozilla.com at Thu, 01 Mar 2018 12:45:47 +0000
Backed out 2 changesets (bug 1426783, bug 1425612) for spidermonekey bustages on non262/extensions/sharedtypedarray.js r=backout on a CLOSED TREE Backed out changeset a8e2b4cf8e26 (bug 1425612) Backed out changeset f10263c3babe (bug 1426783)
a8e2b4cf8e26b900983e33cc2fb6b48f1e5747b2: Bug 1425612 - Better error messages for invalid structured clone data. r=sfink, a=abillings.
Jason Orendorff <jorendorff@mozilla.com> - Sat, 16 Dec 2017 07:16:26 -0600 - rev 452967
Push 1648 by mtabara@mozilla.com at Thu, 01 Mar 2018 12:45:47 +0000
Bug 1425612 - Better error messages for invalid structured clone data. r=sfink, a=abillings.
f10263c3babef5f70e1e8fdb9e52c2de15cf22e1: Bug 1426783 - Fix error handling in deserialization of invalid typed arrays. r=sfink, a=abillings.
Jason Orendorff <jorendorff@mozilla.com> - Fri, 05 Jan 2018 15:17:35 -0600 - rev 452966
Push 1648 by mtabara@mozilla.com at Thu, 01 Mar 2018 12:45:47 +0000
Bug 1426783 - Fix error handling in deserialization of invalid typed arrays. r=sfink, a=abillings.
02f8ce099ade4c097dab1685c58deacc7608cbed: Merge mozilla-central to mozilla-inbound r=merge
Dorel Luca <dluca@mozilla.com> - Thu, 11 Jan 2018 00:05:23 +0200 - rev 452965
Push 1648 by mtabara@mozilla.com at Thu, 01 Mar 2018 12:45:47 +0000
Merge mozilla-central to mozilla-inbound r=merge
28f876e75d47e8c2843332e631145b6a1acf0263: bug 1417680 - explore the feasibility of making XPCOM responsible for shutting down NSS r=jcj r=franziskus r=erahm
David Keeler <dkeeler@mozilla.com> - Fri, 10 Nov 2017 15:03:23 -0800 - rev 452964
Push 1648 by mtabara@mozilla.com at Thu, 01 Mar 2018 12:45:47 +0000
bug 1417680 - explore the feasibility of making XPCOM responsible for shutting down NSS r=jcj r=franziskus r=erahm Historically, PSM has handled tracking NSS resources, releasing them, and shutting down NSS in a coordinated manner (i.e. preventing races, use-after-frees, etc.). This approach has proved intractable. This patch introduces a new approach: have XPCOM shut down NSS after all threads have been joined and the component manager has been shut down (and so there shouldn't be any XPCOM objects holding NSS resources). Note that this patch only attempts to determine if this approach will work. If it does, we will have to go through alter and remove the remnants of the old approach (i.e. nsNSSShutDownPreventionLock and related machinery). This will be done in bug 1421084. MozReview-Commit-ID: LjgEl1UZqkC
6e74b98b535425ea96ecbf65a391e9b6f3f51bc4: Bug 1429174 - Introducing ConsoleUtils for logging messages to console - message level, r=bkelly
Andrea Marchesini <amarchesini@mozilla.com> - Wed, 10 Jan 2018 22:06:38 +0100 - rev 452963
Push 1648 by mtabara@mozilla.com at Thu, 01 Mar 2018 12:45:47 +0000
Bug 1429174 - Introducing ConsoleUtils for logging messages to console - message level, r=bkelly
75a5873327a61af0923c83720a1f677d832e2b9c: Bug 1429174 - Introducing ConsoleUtils for logging messages to console - tests, r=bkelly
Andrea Marchesini <amarchesini@mozilla.com> - Wed, 10 Jan 2018 22:06:37 +0100 - rev 452962
Push 1648 by mtabara@mozilla.com at Thu, 01 Mar 2018 12:45:47 +0000
Bug 1429174 - Introducing ConsoleUtils for logging messages to console - tests, r=bkelly
8c42fc215b1be8456a1c4bb0a1491d9c2bee0ff4: Bug 1429174 - Introducing ConsoleUtils for logging messages to console, r=bkelly
Andrea Marchesini <amarchesini@mozilla.com> - Wed, 10 Jan 2018 22:06:37 +0100 - rev 452961
Push 1648 by mtabara@mozilla.com at Thu, 01 Mar 2018 12:45:47 +0000
Bug 1429174 - Introducing ConsoleUtils for logging messages to console, r=bkelly
b7d96ef3b33c77e7a8fe367d4b6c463a07aac63a: Create a PaintWorker thread pool and dispatch tiles to it (bug 1425056, r=bas)
Ryan Hunt <rhunt@eqrion.net> - Fri, 08 Dec 2017 01:18:05 -0600 - rev 452960
Push 1648 by mtabara@mozilla.com at Thu, 01 Mar 2018 12:45:47 +0000
Create a PaintWorker thread pool and dispatch tiles to it (bug 1425056, r=bas) This commit adds a paint worker thread pool to PaintThread, and dispatches tiled paints to it. The thread pool is only created if tiling is enabled, and its size is set by 'layers.omtp.paint-workers' and defaults to 1. If -1 is specified, it will be sized to 'max((cpu_cores * 3) / 4, 1)'. The one tricky part of dispatching tiled paints to a thread pool is the AsyncEndLayerTransaction message that must execute once all paints are finished. Previously, this runnable would be queued after all the paints had been queued, ensuring it would be run after they had all completed. With a thread pool, there is no guarantee. Instead this commit, uses a flag on CompositorBridgeChild to signify whether all of the paints have been queued ('mOutstandingAsyncEndLayerTransaction'), and after every tiled paint it is examined to see if that paint was the last paint, and if it is to run AsyncEndLayerTransaction. In addition, if the async paints complete before we even mark the end of the layer transaction, we queue it like normal. The profiler markers are also complicated by using a thread pool. I don't know of a great way to keep them working as they are per thread, so for now I've removed them. I may have been the only one using them anyway. MozReview-Commit-ID: 5LIJ9GWSfCn
1cbfd11a64c8e8c790eae0852fa3e492f40282c8: Make a CaptureTiledPaintState for each tile (bug 1425056, r=bas)
Ryan Hunt <rhunt@eqrion.net> - Thu, 07 Dec 2017 23:45:47 -0600 - rev 452959
Push 1648 by mtabara@mozilla.com at Thu, 01 Mar 2018 12:45:47 +0000
Make a CaptureTiledPaintState for each tile (bug 1425056, r=bas) This makes it so that each tile of a paint gets a DrawTargetCapture and its own buffer operations. Once this is done, each CaptureTiledPaintState will be isolated from each other and able to be done in parallel. MozReview-Commit-ID: BuBDXgjma4z
af2ed1a4a02bb8b4c2c3a22589398ecff4fdcba3: Report a DrawTargetTiled as a capture if it is made of captures (bug 1425056, r=bas)
Ryan Hunt <rhunt@eqrion.net> - Wed, 13 Dec 2017 09:27:07 -0600 - rev 452958
Push 1648 by mtabara@mozilla.com at Thu, 01 Mar 2018 12:45:47 +0000
Report a DrawTargetTiled as a capture if it is made of captures (bug 1425056, r=bas) This will make it so that we avoid main thread rasterization for box shadows. MozReview-Commit-ID: 9Tg4dsH21V6
4d88e13db33bf9c01a89475ab423192df94f4628: Make debug bounds checking for FilterNodeSoftware thread safe (bug 1425056, r=mstange)
Ryan Hunt <rhunt@eqrion.net> - Mon, 18 Dec 2017 13:06:30 -0600 - rev 452957
Push 1648 by mtabara@mozilla.com at Thu, 01 Mar 2018 12:45:47 +0000
Make debug bounds checking for FilterNodeSoftware thread safe (bug 1425056, r=mstange) This debug only bounds checking is not thread safe to any filter nodes drawing at the same time. I believe it makes sense to just manually calculate the bounds and pass them along in the functions that need them. MozReview-Commit-ID: 9GiYRbWuVF6
6882857e1bb56a47b975cc7e3fe40fa5443ac6e7: Don't cache SourceSurface's in FilterNodeSoftware (bug 1425056, r=mstange)
Ryan Hunt <rhunt@eqrion.net> - Mon, 18 Dec 2017 12:46:09 -0600 - rev 452956
Push 1648 by mtabara@mozilla.com at Thu, 01 Mar 2018 12:45:47 +0000
Don't cache SourceSurface's in FilterNodeSoftware (bug 1425056, r=mstange) Caching SourceSurfaces on a filter node is not thread safe to multiple threads executing the same filter node at the same time. We could add a mutex to every filter node and guard on that, but I think it makes sense to just remove the caching for now. I'm open to readding this, if this proves to be a problem. MozReview-Commit-ID: Ca38WlG3V89
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip