7b105dde3945a05b7174fbe6d9b61557072315da: Bug 1570681 - Move Eval testing logic from nsContentSecurityManager to nsContentSecurityUtils r=ckerschb
Tom Ritter <tom@mozilla.com> - Wed, 18 Sep 2019 19:36:31 +0000 - rev 494042
Push 114104 by opoprus@mozilla.com at Thu, 19 Sep 2019 10:02:13 +0000
Bug 1570681 - Move Eval testing logic from nsContentSecurityManager to nsContentSecurityUtils r=ckerschb Differential Revision: https://phabricator.services.mozilla.com/D45484
deed0b712be5b49ce52e803a6c71092f1cfe4cf6: Bug 1564475 - Add a native allocation profiling test; r=canaltinova
Greg Tatum <gtatum@mozilla.com> - Wed, 18 Sep 2019 18:47:03 +0000 - rev 494041
Push 114104 by opoprus@mozilla.com at Thu, 19 Sep 2019 10:02:13 +0000
Bug 1564475 - Add a native allocation profiling test; r=canaltinova Differential Revision: https://phabricator.services.mozilla.com/D42198
52fa68b8413b592c8587b35478d84128cdcdf8a1: Bug 1564475 - Add the native allocations feature to the profiler UI; r=canaltinova
Greg Tatum <gtatum@mozilla.com> - Wed, 18 Sep 2019 18:46:51 +0000 - rev 494040
Push 114104 by opoprus@mozilla.com at Thu, 19 Sep 2019 10:02:13 +0000
Bug 1564475 - Add the native allocations feature to the profiler UI; r=canaltinova Differential Revision: https://phabricator.services.mozilla.com/D42197
41a47ecc5c8bd9f8d1224d8ab8f2a43b8681480a: Bug 1564475 - Only turn on the native allocation tracking with a profiler feature; r=njn
Greg Tatum <gtatum@mozilla.com> - Wed, 18 Sep 2019 18:46:39 +0000 - rev 494039
Push 114104 by opoprus@mozilla.com at Thu, 19 Sep 2019 10:02:13 +0000
Bug 1564475 - Only turn on the native allocation tracking with a profiler feature; r=njn The code changes to use a profiler feature for the native allocations were deferred until this commit. Differential Revision: https://phabricator.services.mozilla.com/D42196
57a891548aca1c8e0a8eb4680b1ebc2c17169fd9: Bug 1564475 - Add a mechanism to collect profiler backtraces; r=njn,gerald
Greg Tatum <gtatum@mozilla.com> - Wed, 18 Sep 2019 18:46:19 +0000 - rev 494038
Push 114104 by opoprus@mozilla.com at Thu, 19 Sep 2019 10:02:13 +0000
Bug 1564475 - Add a mechanism to collect profiler backtraces; r=njn,gerald The profiler backtraces inside a memory hook are re-entrant for the profile lock. This patch adds additional guards to protect against this in order to allow for a profiler backtrace during native allocations. Differential Revision: https://phabricator.services.mozilla.com/D42195
11edc7e045e3bd137c504e40c2f8dfebbca0ff84: Bug 1564475 - Disable native allocations when the bloat log is turned on; r=njn
Greg Tatum <gtatum@mozilla.com> - Wed, 18 Sep 2019 18:46:06 +0000 - rev 494037
Push 114104 by opoprus@mozilla.com at Thu, 19 Sep 2019 10:02:13 +0000
Bug 1564475 - Disable native allocations when the bloat log is turned on; r=njn There is a bad interaction between the bloat log and the native allocation tracking. There is a detailed message explaining the problem in the code. Differential Revision: https://phabricator.services.mozilla.com/D42194
3987d16908971d5bdad6f4ce456f51814d5a08b3: Bug 1564475 - Add the ability to collect markers with a Bernoulli trial; r=njn
Greg Tatum <gtatum@mozilla.com> - Wed, 18 Sep 2019 18:45:57 +0000 - rev 494036
Push 114104 by opoprus@mozilla.com at Thu, 19 Sep 2019 10:02:13 +0000
Bug 1564475 - Add the ability to collect markers with a Bernoulli trial; r=njn This commit adds both the native allocation marker, and the Bernoulli trial to attempt to sample the native allocations. Differential Revision: https://phabricator.services.mozilla.com/D42193
2e5fc2937e95818048f12e4f2e550175ccfa56df: Bug 1564475 - Add a mechanism to block re-entry on profiler memory hooks; r=njn
Greg Tatum <gtatum@mozilla.com> - Wed, 18 Sep 2019 18:45:48 +0000 - rev 494035
Push 114104 by opoprus@mozilla.com at Thu, 19 Sep 2019 10:02:13 +0000
Bug 1564475 - Add a mechanism to block re-entry on profiler memory hooks; r=njn This commit adds a ThreadIntercept mechanism to block re-entry when attempting to collect the stacks of native allocations. A following commit will actually hook them up to collect allocations. Differential Revision: https://phabricator.services.mozilla.com/D39882
32930bba2852f1c858be2f2ad640b3f68500e01b: Bug 1564475 - Remove lock failure when removing the profiler counters; r=jesup
Greg Tatum <gtatum@mozilla.com> - Wed, 18 Sep 2019 18:45:44 +0000 - rev 494034
Push 114104 by opoprus@mozilla.com at Thu, 19 Sep 2019 10:02:13 +0000
Bug 1564475 - Remove lock failure when removing the profiler counters; r=jesup The ProfilerCounters had a static lifetime controlled by a UniquePtr. This is an issue if the profiler mutex, which is also static, gets destroyed first. The counters will then try to access the profiler mutex, and find it already destroyed, leading to a crash. This commit changes the life cycle to explicitly leak the counters for the lifteime of the process. In addition, this patch adds explicit install and removal functions for the memory hooks. Differential Revision: https://phabricator.services.mozilla.com/D42192
ca386b968a71fe565ae09f3150f4a98a6b1aa5d4: Bug 1582224 - Split SIDEWAYS bit in WritingMode. r=jfkthame,emilio
Ting-Yu Lin <tlin@mozilla.com> - Thu, 19 Sep 2019 02:37:14 +0000 - rev 494033
Push 114104 by opoprus@mozilla.com at Thu, 19 Sep 2019 10:02:13 +0000
Bug 1582224 - Split SIDEWAYS bit in WritingMode. r=jfkthame,emilio Currently, there's no way to tell whether the SIDEWAYS bit is set from `writing-mode:sideways-*` or `writing-mode:vertical-*; text-orientation:sideways;`. To be able to tell them apart, split SIDEWAYS bits into VERTICAL_SIDEWAYS and TEXT_SIDEWAYS. This is needed by my proposed solution in bug 1102175. Also, provide convenience methods related to sideways writing-mode, and replace obscure checks in the codebase. Note that we don't have the use cases to distinguish vertical-rl from sideways-rl in layout, but for the completeness, IsSidewaysLR() is still defined. Differential Revision: https://phabricator.services.mozilla.com/D46321
30d01b55d02e0ed51cdfb486a1afa4d169461454: Bug 1582217. Drop unneeded image dependencies. r=kvark
Jeff Muizelaar <jrmuizel@gmail.com> - Wed, 18 Sep 2019 22:04:47 +0000 - rev 494032
Push 114104 by opoprus@mozilla.com at Thu, 19 Sep 2019 10:02:13 +0000
Bug 1582217. Drop unneeded image dependencies. r=kvark We only use the png codec so let's save some link time by not including the other codecs. Differential Revision: https://phabricator.services.mozilla.com/D46317
08f2148de71368463e4d72190f237799fec59ae4: Bug 1581757 - Support slicing the scene into an arbitrary number of picture cache slices r=nical
Glenn Watson <github@intuitionlibrary.com> - Wed, 18 Sep 2019 23:17:55 +0000 - rev 494031
Push 114104 by opoprus@mozilla.com at Thu, 19 Sep 2019 10:02:13 +0000
Bug 1581757 - Support slicing the scene into an arbitrary number of picture cache slices r=nical Previously, the setup_picture_caching function was hard coded to support only a very specific shape of display list. With this change, flags are added to PrimitiveCluster that can specify if a picture cache slice should be created before / after this cluster when picture caching is set up. The usage of these flags in this patch matches the old behaviour, so should not have any functional effect. However, in future we will make use of this functionality to create picture slices for a number of different use cases, such as: * Creating cache tiles for the UI. * Slicing the scene where there are video elements, in order to allow these to be composited directly by the OS. This may also apply to WebGL and/or canvas elements. * Slicing the scene when there is a very large fixed position background image or other element, to avoid invalidating the entire tile cache each frame. Differential Revision: https://phabricator.services.mozilla.com/D46125
fa579e9b1e7dc010ff707dd6eae15fef44253f0e: Bug 1575995 - part5 : add gTests r=spohl
Alastor Wu <alwu@mozilla.com> - Fri, 13 Sep 2019 00:13:24 +0000 - rev 494030
Push 114104 by opoprus@mozilla.com at Thu, 19 Sep 2019 10:02:13 +0000
Bug 1575995 - part5 : add gTests r=spohl Differential Revision: https://phabricator.services.mozilla.com/D43317
49618c34643003a9d4ed8584ecdeac18c5927569: Bug 1575995 - part4 : add the pref 'media.hardwaremediakeys.enabled' to control this feature. r=baku
Alastor Wu <alwu@mozilla.com> - Thu, 29 Aug 2019 01:01:04 +0000 - rev 494029
Push 114104 by opoprus@mozilla.com at Thu, 19 Sep 2019 10:02:13 +0000
Bug 1575995 - part4 : add the pref 'media.hardwaremediakeys.enabled' to control this feature. r=baku Differential Revision: https://phabricator.services.mozilla.com/D43316
deb0bc2ec44fcb4af8efca40c6938769e861bd18: Bug 1575995 - part3 : implement play/pause controller. r=chunmin
alwu <alwu@mozilla.com> - Wed, 18 Sep 2019 20:55:57 +0000 - rev 494028
Push 114104 by opoprus@mozilla.com at Thu, 19 Sep 2019 10:02:13 +0000
Bug 1575995 - part3 : implement play/pause controller. r=chunmin The ideal situation for media control should be incooperated with the audio competition so that we only have to control one controller. However, if it's multiple controllers at the same time, we would tend to only control the last one in order to reduce confustion. Ex. If we pause controller A first, and then start controller B. So what should we do when we press `play/pause` hardware key? To resume controller A or to stop controller B, or do both things at the same time? Differential Revision: https://phabricator.services.mozilla.com/D43315
a417c89cf52baa165e3821cce14ed126531e3ee7: Bug 1575995 - part2 : implement the event source on OSX. r=spohl
Alastor Wu <alwu@mozilla.com> - Sat, 14 Sep 2019 03:30:30 +0000 - rev 494027
Push 114104 by opoprus@mozilla.com at Thu, 19 Sep 2019 10:02:13 +0000
Bug 1575995 - part2 : implement the event source on OSX. r=spohl On OSX, we would use the CG event tap to intercept media keys event. Differential Revision: https://phabricator.services.mozilla.com/D43314
239c106912ab92eceb5e7738f0240dd13c268342: Bug 1575995 - part1 : implement basic classes for handling media hardware keys. r=baku
Alastor Wu <alwu@mozilla.com> - Fri, 13 Sep 2019 00:08:57 +0000 - rev 494026
Push 114104 by opoprus@mozilla.com at Thu, 19 Sep 2019 10:02:13 +0000
Bug 1575995 - part1 : implement basic classes for handling media hardware keys. r=baku In order to receive platform level media hardward keys event, we create a `MediaHardwareKeysEventSource` which is used to implement intercepting those events according to different platforms. We can add a `MediaHardwareKeysEventListener` onto `MediaHardwareKeysEventSource`, so that we can get notification whenever hardware media keys are being pressed. `MediaHardwareKeysManager` is used to encapsulate all these details, it would create a source and corresponding listener. Differential Revision: https://phabricator.services.mozilla.com/D43313
9d31a1c17ef8ceb8195db01088bb635e4f575a0f: Bug 1578217 - remove the sync 'yellow state' telemetry. r=tcsc
Mark Hammond <mhammond@skippinet.com.au> - Thu, 19 Sep 2019 00:34:04 +0000 - rev 494025
Push 114104 by opoprus@mozilla.com at Thu, 19 Sep 2019 10:02:13 +0000
Bug 1578217 - remove the sync 'yellow state' telemetry. r=tcsc Differential Revision: https://phabricator.services.mozilla.com/D45765
b6326259d31e1cc9690d5f994e7fee7a7d7e19be: Bug 1578661 - Add a crappy histogram parser for the devtools database, for probe-scraper. r=chutten
Emilio Cobos Álvarez <emilio@crisal.io> - Thu, 19 Sep 2019 00:20:12 +0000 - rev 494024
Push 114104 by opoprus@mozilla.com at Thu, 19 Sep 2019 10:02:13 +0000
Bug 1578661 - Add a crappy histogram parser for the devtools database, for probe-scraper. r=chutten (And test it.) Differential Revision: https://phabricator.services.mozilla.com/D46111
b03efe57fcd6fa1d14875316ba354ab00419c7fe: Bug 1578661 - Add a note about CSS use counters to the documentation. r=chutten
Emilio Cobos Álvarez <emilio@crisal.io> - Thu, 19 Sep 2019 00:20:12 +0000 - rev 494023
Push 114104 by opoprus@mozilla.com at Thu, 19 Sep 2019 10:02:13 +0000
Bug 1578661 - Add a note about CSS use counters to the documentation. r=chutten Not sure how much detail does it need (it just works) but suggestions welcome. Differential Revision: https://phabricator.services.mozilla.com/D45929
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 tip