aec659045f35f04f7d9ac319665d640a2ccd0a88: Backed out 2 changesets (bug 1358372) for leaks in many tests. a=backout
Sebastian Hengst <archaeopteryx@coole-files.de> - Wed, 14 Feb 2018 20:37:30 +0200 - rev 454862
Push 1648 by mtabara@mozilla.com at Thu, 01 Mar 2018 12:45:47 +0000
Backed out 2 changesets (bug 1358372) for leaks in many tests. a=backout Backed out changeset 444056446ee9 (bug 1358372) Backed out changeset e9139fb87c85 (bug 1358372)
6ca6a81f6f32e1e168ceec1a2f09766d9222bfe2: Bug 1435296 Address xpcshell test failures from increasing timer precision r=baku a=ritu
Tom Ritter <tom@mozilla.com> - Wed, 14 Feb 2018 11:44:18 -0600 - rev 454861
Push 1648 by mtabara@mozilla.com at Thu, 01 Mar 2018 12:45:47 +0000
Bug 1435296 Address xpcshell test failures from increasing timer precision r=baku a=ritu
24cb1a9d9b2357a508cbeeb94fa5c207cd4a8064: Bug 1435296 Clean 0ms durations in stub generation r=nchevobbe a=ritu
Tom Ritter <tom@mozilla.com> - Fri, 09 Feb 2018 19:31:52 -0600 - rev 454860
Push 1648 by mtabara@mozilla.com at Thu, 01 Mar 2018 12:45:47 +0000
Bug 1435296 Clean 0ms durations in stub generation r=nchevobbe a=ritu If the duration was 0ms, it would not be cleaned; and thus lead to a mismatch and ultimately test failure. MozReview-Commit-ID: 1s9nMzlGT0e
9012bf881e43f794e40ef930d888660407c9ea08: Bug 1435296 Update the CSS Animations tests to handle our new Timer Precision decision r=baku a=ritu
Tom Ritter <tom@mozilla.com> - Wed, 07 Feb 2018 20:35:38 -0600 - rev 454859
Push 1648 by mtabara@mozilla.com at Thu, 01 Mar 2018 12:45:47 +0000
Bug 1435296 Update the CSS Animations tests to handle our new Timer Precision decision r=baku a=ritu This commit does several subtle things. 1: It changes ok() to opener.ok() ok is not defined, we have to use opener.ok. This was not caught before because this call is used to provide additional debugging information when a test fails. Test didn't fail, didn't hit that line. 2: It disables the call to opener.ok() we just fixed. As the comment there describes, we expect that function to fail, so we don't want to assert(false). 3: It inverts failures to successes if only the reduceTimerPrecision pref is set MozReview-Commit-ID: lpKKhJoDs6
576378b59e73dd5dd65a7349bd7e4bf89b04df1c: Bug 1435296 Address test failures caused by bumping timer precision to 2 ms r=baku a=ritu
Tom Ritter <tom@mozilla.com> - Wed, 14 Feb 2018 11:32:05 -0600 - rev 454858
Push 1648 by mtabara@mozilla.com at Thu, 01 Mar 2018 12:45:47 +0000
Bug 1435296 Address test failures caused by bumping timer precision to 2 ms r=baku a=ritu There are a few different reasons why tests needed updating (not an exhaustive list): - Tests assume that successive operations take place at different times. - Tests assume that an operation took a minimum amount of time. - Tests hardcodes a specific delay. In most cases we hardcode the preference off. In some cases this is the best approach, in others, we would like to improve. The bug for tracking those improvements is Bug 1429648 An improvement that is present in some tests is to hardcode a specific precision reduction that is acceptable based on the confides of the test. (Obviously this needs to be a fix for the test framework and not a requirement on the feature being tested.) In a few places, the test itself can be fixed, for example to no longer require the end time of an operation to be strictly greater than the start time, and allows it to be equal to it.
96bc5f3e459189cc1b576d028e60a957a37a4a7e: Bug 1435296 Do not apply timer clamping to CSS animations. r=birtles a=ritu
Tom Ritter <tom@mozilla.com> - Wed, 07 Feb 2018 16:50:57 -0600 - rev 454857
Push 1648 by mtabara@mozilla.com at Thu, 01 Mar 2018 12:45:47 +0000
Bug 1435296 Do not apply timer clamping to CSS animations. r=birtles a=ritu This patch creates the capability to have callsites specify if timestamps should be clamped only in Resist Fingerprinting Mode, or in the more expansive Timer PRecision Reduction Mode. Then it changes the CSS Animation callsite to only apply in RFP Mode. This avoids regressing RFP. MozReview-Commit-ID: B1pSri0kRk6
3cba8d67a642f6ff0166812c77c83d72422336d7: Bug 1435296 Bump the default timer precision resolution to 2ms r=baku a=ritu
Tom Ritter <tom@mozilla.com> - Fri, 02 Feb 2018 11:05:40 -0600 - rev 454856
Push 1648 by mtabara@mozilla.com at Thu, 01 Mar 2018 12:45:47 +0000
Bug 1435296 Bump the default timer precision resolution to 2ms r=baku a=ritu MozReview-Commit-ID: G33jNNJVRSU
cb850e0aad33c42bc4723d38bee99b7423a37731: no bug - Bumping Firefox l10n changesets DONTBUILD r=release a=l10n-bump
L10n Bumper Bot <release+l10nbumper@mozilla.com> - Wed, 14 Feb 2018 10:19:34 -0800 - rev 454855
Push 1648 by mtabara@mozilla.com at Thu, 01 Mar 2018 12:45:47 +0000
no bug - Bumping Firefox l10n changesets DONTBUILD r=release a=l10n-bump be -> df94b39fa61f cak -> 5adbe6a9f2a1 cy -> eb2a743b3721 eo -> 2899bffb451e fy-NL -> ef357b21a997 gu-IN -> 388a587f6555 is -> 28f12f503ac3 it -> 08a781c39267 pt-BR -> e8ed70034c4b sq -> 8071d86700f8
60cfaa3766ecf409ecbaae67f640fe22bc47e875: no bug - Bumping Fennec l10n changesets DONTBUILD r=release a=l10n-bump
L10n Bumper Bot <release+l10nbumper@mozilla.com> - Wed, 14 Feb 2018 10:19:28 -0800 - rev 454854
Push 1648 by mtabara@mozilla.com at Thu, 01 Mar 2018 12:45:47 +0000
no bug - Bumping Fennec l10n changesets DONTBUILD r=release a=l10n-bump is -> 28f12f503ac3
d5b7bbc956d67e9c28c408bd2d34c85f5fe5411c: Bug 1437213 - Revert top site pref to show 1 row instead of 2 rows for 59. r=dmose a=ritu on a CLOSED TREE
Ed Lee <edilee@mozilla.com> - Fri, 09 Feb 2018 15:48:15 -0800 - rev 454853
Push 1648 by mtabara@mozilla.com at Thu, 01 Mar 2018 12:45:47 +0000
Bug 1437213 - Revert top site pref to show 1 row instead of 2 rows for 59. r=dmose a=ritu on a CLOSED TREE MozReview-Commit-ID: 8mblhw6IoJ
4e1f1641976cd22428ba7bbec063d2eb8ff9c8cb: Bug 1436517 - Limit access to the server-timing header to HTTPS contexts. r=mcmanus a=ritu
Nicholas Hurley <hurley@mozilla.com> - Wed, 07 Feb 2018 16:05:38 -0800 - rev 454852
Push 1648 by mtabara@mozilla.com at Thu, 01 Mar 2018 12:45:47 +0000
Bug 1436517 - Limit access to the server-timing header to HTTPS contexts. r=mcmanus a=ritu This also introduces a hidden pref to allow server-timing access from HTTP contexts for the purposes of our xpcshell tests. We'll remove that once we get h2 (and therefore tls test) support for server-timing trailers (https://bugzilla.mozilla.org/show_bug.cgi?id=1436601). This does not reject or otherwise error when receiving server-timing headers or trailers on non-HTTPS contexts, it just makes it unavailable outside the channel. MozReview-Commit-ID: qi4h0VQknE
ff9753468f8c52fb2c29ab76bc888675335bee26: Bug 1436466 - Set dirty in CopyableCanvasRenderer::ClearCachedResources() r=jrmuizel a=ritu
sotaro <sotaro.ikeda.g@gmail.com> - Sat, 10 Feb 2018 08:13:52 +0900 - rev 454851
Push 1648 by mtabara@mozilla.com at Thu, 01 Mar 2018 12:45:47 +0000
Bug 1436466 - Set dirty in CopyableCanvasRenderer::ClearCachedResources() r=jrmuizel a=ritu bug 1379920 changed the way of dirty flag handling. And the dirty flag was not set when CopyableCanvasRenderer::ClearCachedResources() is called. Then ShareableCanvasRenderer::UpdateCompositableClient() did not update canvas.
2e8b4957bf5f477c66ef4da8390426d261b1daf2: bug 1436267 fallback from audio callback to system clock driver on error only once r=padenot a=ritu
Karl Tomlinson <karlt+@karlt.net> - Wed, 07 Feb 2018 20:16:01 +1300 - rev 454850
Push 1648 by mtabara@mozilla.com at Thu, 01 Mar 2018 12:45:47 +0000
bug 1436267 fallback from audio callback to system clock driver on error only once r=padenot a=ritu Usually, mShouldFallbackIfError has been reset to false in DataCallback() before Stop() is called. However, if fallback to a system clock driver due to cubeb error had already occurred, then mShouldFallbackIfError would not have been reset, and Stop() is still called. With mShouldFallbackIfError still true, a cubeb error in stop would have created another fallback thread. I expect that resetting mShouldFallbackIfError in Stop() would also be an effective alternative solution, but resetting on StateCallback() happens earlier, which would be an advantage if any additional errors could possibly be reported to StateCallback(). MozReview-Commit-ID: E9j7PQmS3O4
1b25b61d773b47ad1ca081c2c88b0ae9286a38d3: Bug 1434861 - Simplify rescaling code in MediaEngineRemoteVideoSource::DeliverFrame. r=jib a=ritu
Andreas Pehrson <pehrsons@mozilla.com> - Thu, 01 Feb 2018 16:06:19 +0100 - rev 454849
Push 1648 by mtabara@mozilla.com at Thu, 01 Mar 2018 12:45:47 +0000
Bug 1434861 - Simplify rescaling code in MediaEngineRemoteVideoSource::DeliverFrame. r=jib a=ritu Most importantly, this reduces the number of copies to 1 in the common case. In a case where we are rescaling because there are competing gUM requests this does two copies, where one is the crop-and-scale operation itself. In the worst case we do two allocations, but with a buffer pool and a recycling ImageContainer we allocate very rarely in practice. MozReview-Commit-ID: B0Et4wZol9n
cb55e5e2cdd5eb7e953b73f4bfce6c14a38b1c35: Bug 1433869 - Disable CSD titlebar mode on untested/unknown systems for Release/Beta, r=jhorak a=ritu
Martin Stransky <stransky@redhat.com> - Mon, 29 Jan 2018 11:35:31 +0100 - rev 454848
Push 1648 by mtabara@mozilla.com at Thu, 01 Mar 2018 12:45:47 +0000
Bug 1433869 - Disable CSD titlebar mode on untested/unknown systems for Release/Beta, r=jhorak a=ritu MozReview-Commit-ID: JRF0BAbtkRN
38c1798e2a2e7d06733f1d715af22d3d44d454e7: Bug 1432411: Wallpaper over the case where there is no Screen. r=jgilbert a=ritu
Milan Sreckovic <milan@mozilla.com> - Fri, 09 Feb 2018 13:42:17 -0500 - rev 454847
Push 1648 by mtabara@mozilla.com at Thu, 01 Mar 2018 12:45:47 +0000
Bug 1432411: Wallpaper over the case where there is no Screen. r=jgilbert a=ritu MozReview-Commit-ID: ISeBw7qxGdH
0128f159f3a3aabd70b0b6bddc50255c907bc7a6: Bug 1432385 - Use window manager borders on LXQt, r=jhorak a=ritu
Martin Stransky <stransky@redhat.com> - Thu, 25 Jan 2018 15:52:06 +0100 - rev 454846
Push 1648 by mtabara@mozilla.com at Thu, 01 Mar 2018 12:45:47 +0000
Bug 1432385 - Use window manager borders on LXQt, r=jhorak a=ritu MozReview-Commit-ID: JkyBMBovCIG
31a1ad5257ecfd6b3d5d79c34c3ff286d390d77e: Bug 1432160 - Initialize PushService for custom tabs / PWA; r=snorp a=ritu
Jim Chen <nchen@mozilla.com> - Thu, 08 Feb 2018 18:33:19 -0500 - rev 454845
Push 1648 by mtabara@mozilla.com at Thu, 01 Mar 2018 12:45:47 +0000
Bug 1432160 - Initialize PushService for custom tabs / PWA; r=snorp a=ritu We currently initialize PushService on delayed startup, which only happens when Fennec is launched. This patch makes us also initialize PushService if needed by web content from custom tabs / PWA, by listening for the push initialization event in GeckoApplication. MozReview-Commit-ID: 9CTOEZmOqls
6f99bde986e07b6606f172483ce0e1384fd22bd9: Bug 1431264 part 3: AccessibleHandler: If a client wants to query all relations, fetch as much info as possible in a single cross-process call. r=MarcoZ a=ritu
James Teh <jteh@mozilla.com> - Fri, 02 Feb 2018 09:38:51 +1000 - rev 454844
Push 1648 by mtabara@mozilla.com at Thu, 01 Mar 2018 12:45:47 +0000
Bug 1431264 part 3: AccessibleHandler: If a client wants to query all relations, fetch as much info as possible in a single cross-process call. r=MarcoZ a=ritu If a client calls IAccessible2::nRelations, it's likely that it will next call IAccessible2::relations to query each relation. Furthermore, it's likely the client will call relationType and nTargets on each relation. Therefore, fetch all of this info when nRelations is called. The number of relations is immediately returned to the client. The rest of the info is cached and returned to the client when the appropriate methods are called. The info is only cached for one call; i.e. after the client calls relations once, the cache is dropped. This makes memory management simpler and lowers the risk of cache invalidation problems. MozReview-Commit-ID: IBoJbu42osG
617e767b8af15c1d81f1f512193c76747837c62f: Bug 1431264 part 2: AccessibleHandler: Local implementation of IAccessibleRelation using data provided in IARelationData. r=MarcoZ a=ritu
James Teh <jteh@mozilla.com> - Fri, 02 Feb 2018 09:35:16 +1000 - rev 454843
Push 1648 by mtabara@mozilla.com at Thu, 01 Mar 2018 12:45:47 +0000
Bug 1431264 part 2: AccessibleHandler: Local implementation of IAccessibleRelation using data provided in IARelationData. r=MarcoZ a=ritu The HandlerProvider::RelationsInfo method provides the type and number of targets for each relation in an IARelationData struct. This local implementaition of IAccessibleRelation is constructed with an IARelationData struct and serves a single relation. It uses the data from the struct to answer queries, except for actual targets. For targets, it makes a remote call to IA2_2::relationTargetsOfType to answer the query. We use relationTargetsOfType instead of IARelation::targets because marshaling so many IARelation pointers is a major bottleneck. MozReview-Commit-ID: Dva00FhoSbx
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip