beb5f00c4b195c51fc8cb37ae21068bd21b4138f: bug 1366294 - Part 9 - Fix Windows Build. r=gfritzsche
Chris H-C <chutten@mozilla.com> - Wed, 28 Jun 2017 11:00:41 -0700 - rev 418460
Push 7566 by mtabara@mozilla.com at Wed, 02 Aug 2017 08:25:16 +0000
bug 1366294 - Part 9 - Fix Windows Build. r=gfritzsche MozReview-Commit-ID: 8P2W8fD2xNi
72635bc1ba2511e8e9ce7303982e8b89d1d050aa: bug 1366294 - Part 8 - Include a message on telemetry testfails. r=gfritzsche
Chris H-C <chutten@mozilla.com> - Fri, 23 Jun 2017 16:39:59 -0400 - rev 418459
Push 7566 by mtabara@mozilla.com at Wed, 02 Aug 2017 08:25:16 +0000
bug 1366294 - Part 8 - Include a message on telemetry testfails. r=gfritzsche I just added some short identifiable messages to help identify which part of the test failed. MozReview-Commit-ID: 3AX2iucGiRx
c387459a798bbc74ace160813e18563aca8ca94e: bug 1366294 - Part 7 - Use keyed histogram snaphots to build payloads. r=gfritzsche
Chris H-C <chutten@mozilla.com> - Fri, 23 Jun 2017 16:38:21 -0400 - rev 418458
Push 7566 by mtabara@mozilla.com at Wed, 02 Aug 2017 08:25:16 +0000
bug 1366294 - Part 7 - Use keyed histogram snaphots to build payloads. r=gfritzsche TelemetrySession's getKeyedHistograms asks for each keyed histogram individually. This is inefficient and doesn't work well with the storage refactor. So, plumb through a subsession keyed histogram snapshot API and convert TelemetrySession over to using it. MozReview-Commit-ID: Af9dTqw99UA
476daf9a58465e1954419c874148493cbac534cc: bug 1366294 - Part 6 - Update test_TelemetryHistograms for new snapshots format r=gfritzsche
Chris H-C <chutten@mozilla.com> - Fri, 23 Jun 2017 15:15:11 -0400 - rev 418457
Push 7566 by mtabara@mozilla.com at Wed, 02 Aug 2017 08:25:16 +0000
bug 1366294 - Part 6 - Update test_TelemetryHistograms for new snapshots format r=gfritzsche MozReview-Commit-ID: FN6y1zTqFt4
e7ce6a06c131dfe37ceea24a3b09a5b5d6475127: bug 1366294 - Part 5 - Send appropriately-structured Telemetry data to JS r=gfritzsche
Chris H-C <chutten@mozilla.com> - Tue, 20 Jun 2017 15:03:10 -0400 - rev 418456
Push 7566 by mtabara@mozilla.com at Wed, 02 Aug 2017 08:25:16 +0000
bug 1366294 - Part 5 - Send appropriately-structured Telemetry data to JS r=gfritzsche Previously we were doing bad string manipulation nonsense. Now when asked for snapshots C++ can return a properly-formated Object tree. MozReview-Commit-ID: HAvIbgzUvMU
1cc736607aab9744c015e9dc0734dc35511db825: bug 1366294 - Part 4 - Small cleanups to previous patches. r=gfritzsche
Chris H-C <chutten@mozilla.com> - Fri, 23 Jun 2017 16:42:21 -0400 - rev 418455
Push 7566 by mtabara@mozilla.com at Wed, 02 Aug 2017 08:25:16 +0000
bug 1366294 - Part 4 - Small cleanups to previous patches. r=gfritzsche MozReview-Commit-ID: 7PioVNfUUNZ
175c3ccb00155c5fe5426fbd7b1f0faa70aca11b: Bug 1366294 - Part 3 - Refactor TelemetryHistogram storage. r=chutten
Georg Fritzsche <georg.fritzsche@googlemail.com> - Thu, 08 Jun 2017 16:15:38 +0700 - rev 418454
Push 7566 by mtabara@mozilla.com at Wed, 02 Aug 2017 08:25:16 +0000
Bug 1366294 - Part 3 - Refactor TelemetryHistogram storage. r=chutten Previously we used the base::StatisticsRecorder object for storage by name. This is keyed by histogram name, which doesn't match our storage reality anymore. Instead we use a name to refer to a set of histogram instances that record data from different processes, as well as separating session and subsession data. In this re-write, we instead introduce the following lookup paths (managed in TelemetryHistogram.cpp): - Main storage: - (histogramId, processId, sessionOrSubsession) -> Histogram* - (histogramId, processId) -> KeyedHistogram* (this handles subsessions internally) - Lookup: - (histogramName) -> histogramId - (HistogramID) -> bool (is recording enabled for this histogram?) This is wrapped with a few lookup functions. This also allows us to keep HistogramIDs in the JS histogram instances now, instead of pointers to Histogram instances. That means Histogram instance life-time management is now properly contained inside TelemetryHistogram.cpp. MozReview-Commit-ID: 5yijGv7mc89
96b594816a21fcafb313b710211ccfa6b1a4237e: Bug 1366294 - Part 2 - Cleanup Chromium Histogram code. r=chutten
Georg Fritzsche <georg.fritzsche@googlemail.com> - Tue, 06 Jun 2017 16:48:11 +0700 - rev 418453
Push 7566 by mtabara@mozilla.com at Wed, 02 Aug 2017 08:25:16 +0000
Bug 1366294 - Part 2 - Cleanup Chromium Histogram code. r=chutten - A histogram name identifies a set of histogram instances, for which storage and lookup will be handled in TelemetryHistogram.cpp. So we remove the names from histogram code. - Various unused macros in the header are removed. - Remaining traces of StatisticsRecorder are removed from the Histogram class code. - Some unused methods are dropped that were about printing histograms to ASCII etc. MozReview-Commit-ID: BF2rLSpKOJ8
57400dd449ad5dd77f88054e06c647023eaa3866: Bug 1366294 - Part 1 - Remove base::StatisticsRecorder. r=chutten
Georg Fritzsche <georg.fritzsche@googlemail.com> - Sat, 03 Jun 2017 01:09:11 +0700 - rev 418452
Push 7566 by mtabara@mozilla.com at Wed, 02 Aug 2017 08:25:16 +0000
Bug 1366294 - Part 1 - Remove base::StatisticsRecorder. r=chutten The Chromium IPC histogram code used the StatisticsRecorder object for storage. This is keyed by histogram name, which doesn't match our storage reality anymore. Instead we use a name to refer to a set of histogram instances that record data from different processes, as well as separating session and subsession data. Consequently we need to rewrite this storage, which means StatisticsRecorder is not used anymore. MozReview-Commit-ID: 1LC7YubpKaD
cf1afed54d07d18524b35395d427cc840caf5019: Bug 1379643: When running under sandbox level >= 3, parent should retain IStream of marshaled interface to be destroyed later; r=jimm
Aaron Klotz <aklotz@mozilla.com> - Wed, 19 Jul 2017 12:07:45 -0600 - rev 418451
Push 7566 by mtabara@mozilla.com at Wed, 02 Aug 2017 08:25:16 +0000
Bug 1379643: When running under sandbox level >= 3, parent should retain IStream of marshaled interface to be destroyed later; r=jimm MozReview-Commit-ID: Egb6Yahdbxm
24dc2160940436a8d5bfcf2a591c7936df0f00ee: Bug 1379280 - Only do async keyboard scrolling for a selection, not a focused element. r=smaug
Ryan Hunt <rhunt@eqrion.net> - Thu, 13 Jul 2017 15:53:26 -0500 - rev 418450
Push 7566 by mtabara@mozilla.com at Wed, 02 Aug 2017 08:25:16 +0000
Bug 1379280 - Only do async keyboard scrolling for a selection, not a focused element. r=smaug This commit changes async keyboard scrolling to be enabled only if the content to scroll is from a selection. This works around the problem of detecting whether an arbitrary element has key listeners that should prevent async key scrolling, because when they have the focus we will have disabled async key scrolling. MozReview-Commit-ID: 6HhSuGZNsMX
5b0d1fdf2d20b75caf46d07af956ba5251674359: Bug 1379280 - Move FocusTarget include from nsIPresShell to PresShell. r=smaug
Ryan Hunt <rhunt@eqrion.net> - Thu, 13 Jul 2017 13:00:21 -0500 - rev 418449
Push 7566 by mtabara@mozilla.com at Wed, 02 Aug 2017 08:25:16 +0000
Bug 1379280 - Move FocusTarget include from nsIPresShell to PresShell. r=smaug FocusTarget used to be needed in nsIPresShell, but it was moved to PresShell. MozReview-Commit-ID: HQFpT9OJaUz
6d68d842f601c310626d2ccedab94b38da321b72: Bug 1381736 - Fix modifier masks for APZ keyboard shortcuts. r=masayuki
Ryan Hunt <rhunt@eqrion.net> - Tue, 18 Jul 2017 02:03:14 -0400 - rev 418448
Push 7566 by mtabara@mozilla.com at Wed, 02 Aug 2017 08:25:16 +0000
Bug 1381736 - Fix modifier masks for APZ keyboard shortcuts. r=masayuki MozReview-Commit-ID: LGQzHabEqrz
f15bf893f71fb75f4c8c4b3a17994c5531408368: Bug 1381930: Move JitFrameIterator methods to their own cpp file; r=nbp
Benjamin Bouvier <benj@benj.me> - Tue, 18 Jul 2017 20:10:48 +0200 - rev 418447
Push 7566 by mtabara@mozilla.com at Wed, 02 Aug 2017 08:25:16 +0000
Bug 1381930: Move JitFrameIterator methods to their own cpp file; r=nbp MozReview-Commit-ID: 6ShujTv5EIM
33cf2dcc5aaf1819ee5099defab131afb51e76fd: Bug 1381930: Use delegating ctors for JitFrameIterator; r=nbp
Benjamin Bouvier <benj@benj.me> - Tue, 18 Jul 2017 19:36:25 +0200 - rev 418446
Push 7566 by mtabara@mozilla.com at Wed, 02 Aug 2017 08:25:16 +0000
Bug 1381930: Use delegating ctors for JitFrameIterator; r=nbp MozReview-Commit-ID: 1tmUQ9yPQSd
6b8a76e20661787f7b17e3a4c8ff1f030c30529b: Bug 1382040: Fix benign assertion issue when decoding wasm names; r=luke
Benjamin Bouvier <benj@benj.me> - Wed, 19 Jul 2017 12:15:19 +0200 - rev 418445
Push 7566 by mtabara@mozilla.com at Wed, 02 Aug 2017 08:25:16 +0000
Bug 1382040: Fix benign assertion issue when decoding wasm names; r=luke MozReview-Commit-ID: KPefZhEo5si
5eeb5b9f118b819bebb8ef8cc2c06cdb6b412761: Bug 1379282 - Improve XPCOM's pointer hashing functions for pointers to neighboring memory locations; r=erahm
Ehsan Akhgari <ehsan@mozilla.com> - Fri, 07 Jul 2017 16:54:16 -0400 - rev 418444
Push 7566 by mtabara@mozilla.com at Wed, 02 Aug 2017 08:25:16 +0000
Bug 1379282 - Improve XPCOM's pointer hashing functions for pointers to neighboring memory locations; r=erahm The simplistic shift-based hashing function creates a lot of collisions for pointers pointing to arrays as it doesn't do a great job at distributing the data randomly based on the input bytes.
09deb3ef1f63354a1d4716826c4ccbec1d730db4: Bug 1359833 - Part 10. Add telemetry to track how often imgRequestProxy needs to dispatch. r=tnikkel data-r=bsmedberg
Andrew Osmond <aosmond@mozilla.com> - Wed, 19 Jul 2017 14:15:12 -0400 - rev 418443
Push 7566 by mtabara@mozilla.com at Wed, 02 Aug 2017 08:25:16 +0000
Bug 1359833 - Part 10. Add telemetry to track how often imgRequestProxy needs to dispatch. r=tnikkel data-r=bsmedberg
b44a7fd7a4175d0e705245ec74267e2d16d8cc6f: Bug 1359833 - Part 9. Fix image mochitests to not assume a particular order of events. r=tnikkel
Andrew Osmond <aosmond@mozilla.com> - Wed, 19 Jul 2017 14:15:12 -0400 - rev 418442
Push 7566 by mtabara@mozilla.com at Wed, 02 Aug 2017 08:25:16 +0000
Bug 1359833 - Part 9. Fix image mochitests to not assume a particular order of events. r=tnikkel
b63d906a88b55c62d0fe3eafc09a5a0c1da3bc03: Bug 1359833 - Part 8. ScriptedNotificationObserver should use nsAutoScriptBlocker when issuing notifications. r=tnikkel
Andrew Osmond <aosmond@mozilla.com> - Wed, 19 Jul 2017 14:15:12 -0400 - rev 418441
Push 7566 by mtabara@mozilla.com at Wed, 02 Aug 2017 08:25:16 +0000
Bug 1359833 - Part 8. ScriptedNotificationObserver should use nsAutoScriptBlocker when issuing notifications. r=tnikkel
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip