61f204267373b1806950985a5b5abd4933f15009: Bug 1441333: Part 2 - Allow passing an error stack to reportError. r=bz
Kris Maglione <maglione.k@gmail.com> - Thu, 01 Mar 2018 13:57:27 -0800 - rev 445117
Push 8 by bugmail@asutherland.org at Sat, 11 Aug 2018 16:11:21 +0000
Bug 1441333: Part 2 - Allow passing an error stack to reportError. r=bz Building on top of part 1, we need a way to link a saved caller location to a reported error message. This change allows us to pass a stack to `reportError` when called with a string. This part was written before part 3, and could probably be removed in favor of using createError in every call. But this method also has the advantage of being more consise and somewhate more efficient. MozReview-Commit-ID: 39jfCg9AerY
f9eb113f179f94145a575f602e359186d71b2b34: Bug 1441333: Part 1 - Add helper to retrieve closest stack frame with a given principal. r=bz
Kris Maglione <maglione.k@gmail.com> - Sat, 11 Nov 2017 17:39:16 -0800 - rev 445116
Push 8 by bugmail@asutherland.org at Sat, 11 Aug 2018 16:11:21 +0000
Bug 1441333: Part 1 - Add helper to retrieve closest stack frame with a given principal. r=bz Most WebExtension APIs are async, and have fairly complicated error reporting semantics. As a result, when we report an error, the current JS stack has very little to do with the JS caller that triggered the error, which makes it difficult to diagnose. In order to improve the situation, we need to store the location of the caller at the start of an async operation, so we can tie the error to some marginally useful location. We don't have a reasonable way to do that now other than proactively creating an error object when the API is called, or creating a promise with a full async stack, both of which are too expensive. This helper instead returns a single SavedStack frame with a given principal, which should be considerably cheaper, and likely good enough to give a starting point for debugging cryptic errors. MozReview-Commit-ID: BTxhpZK9Fdz
4e681b986b5cdd36dbb8b50c232b8b5d4db8e4f3: Bug 1440816: Part 1 - Set readPrincipals callback on JS context. r=fitzgen
Kris Maglione <maglione.k@gmail.com> - Fri, 23 Feb 2018 17:20:32 -0800 - rev 445115
Push 8 by bugmail@asutherland.org at Sat, 11 Aug 2018 16:11:21 +0000
Bug 1440816: Part 1 - Set readPrincipals callback on JS context. r=fitzgen MozReview-Commit-ID: L9SQ5tiHkl5
df0e967f8e8fa30a69338008b6ee296bf5e9c545: Bug 1441488 followup, remove incorrect annotation that webdriver/tests/navigation/current_url.py fails on Linux debug, since it doesn't, a=permaorange
Phil Ringnalda <philringnalda@gmail.com> - Thu, 01 Mar 2018 20:34:33 -0800 - rev 445114
Push 8 by bugmail@asutherland.org at Sat, 11 Aug 2018 16:11:21 +0000
Bug 1441488 followup, remove incorrect annotation that webdriver/tests/navigation/current_url.py fails on Linux debug, since it doesn't, a=permaorange
f8688efe482431851107b74a1dd9815f3292a8b7: Bug 1441424 - Fix autoplay activation test. r=kamidphish
Chris Pearce <cpearce@mozilla.com> - Thu, 01 Mar 2018 17:21:09 +1300 - rev 445113
Push 8 by bugmail@asutherland.org at Sat, 11 Aug 2018 16:11:21 +0000
Bug 1441424 - Fix autoplay activation test. r=kamidphish Post landing of bug 1193394 test_autoplay_policy_activation was failing. This is because we weren't clicking the child frame properly in the test. Fix the test, and re-enable. MozReview-Commit-ID: Ius4GWIX8Ng
b59a2fcd3435ec59ceaea010324db3761edb596e: Bug 1440867 - Only poison nursery chunks that were used when clearing, r=jonco
Steve Fink <sfink@mozilla.com> - Fri, 23 Feb 2018 19:55:08 -0800 - rev 445112
Push 8 by bugmail@asutherland.org at Sat, 11 Aug 2018 16:11:21 +0000
Bug 1440867 - Only poison nursery chunks that were used when clearing, r=jonco
4000e7883aefcc7886a7eabb43ac6b9e592a0066: Backed out changeset 8ac015e40755 (bug 1441153) for web platform tests failre on media files
Dorel Luca <dluca@mozilla.com> - Fri, 02 Mar 2018 04:06:22 +0200 - rev 445111
Push 8 by bugmail@asutherland.org at Sat, 11 Aug 2018 16:11:21 +0000
Backed out changeset 8ac015e40755 (bug 1441153) for web platform tests failre on media files
eec4330cfdb35bd38ce21fd78e7ba04af3a5e4a7: Backed out 6 changesets (bug 1425462) for XPCShell failure on multiple files
Dorel Luca <dluca@mozilla.com> - Fri, 02 Mar 2018 03:33:17 +0200 - rev 445110
Push 8 by bugmail@asutherland.org at Sat, 11 Aug 2018 16:11:21 +0000
Backed out 6 changesets (bug 1425462) for XPCShell failure on multiple files Backed out changeset 9ace3811f525 (bug 1425462) Backed out changeset 7d440e52e3a4 (bug 1425462) Backed out changeset 85896ea96faf (bug 1425462) Backed out changeset 127b5d2e6779 (bug 1425462) Backed out changeset 95ce64d3a29a (bug 1425462) Backed out changeset ddd2c4da4ba4 (bug 1425462)
bd9a72daf25192fca6365a616566f91a21c19daa: Backed out changeset 45ae173a1348 (bug 1418749) for widget leaks on Mochitests
Dorel Luca <dluca@mozilla.com> - Fri, 02 Mar 2018 02:50:08 +0200 - rev 445109
Push 8 by bugmail@asutherland.org at Sat, 11 Aug 2018 16:11:21 +0000
Backed out changeset 45ae173a1348 (bug 1418749) for widget leaks on Mochitests
9ace3811f52568b96352e578099a79e8732f177f: Bug 1425462 Refactor the static members into static globals to avoid leakchecks r=ckerschb
Tom Ritter <tom@mozilla.com> - Thu, 01 Mar 2018 05:24:36 -0600 - rev 445108
Push 8 by bugmail@asutherland.org at Sat, 11 Aug 2018 16:11:21 +0000
Bug 1425462 Refactor the static members into static globals to avoid leakchecks r=ckerschb MozReview-Commit-ID: 2lm1Skf3KEH
7d440e52e3a4862bfd981c0f0d09d13d03689581: Bug 1425462 Turn jitter on by default r=luke
Tom Ritter <tom@mozilla.com> - Thu, 15 Feb 2018 15:35:42 -0600 - rev 445107
Push 8 by bugmail@asutherland.org at Sat, 11 Aug 2018 16:11:21 +0000
Bug 1425462 Turn jitter on by default r=luke MozReview-Commit-ID: 9u0rJ8FoteG
85896ea96faf2f55b4401674b1c469c7d9be513d: Bug 1425462 Sprinkle some thread safety on the LRU Cache r=handyman
Tom Ritter <tom@mozilla.com> - Sat, 24 Feb 2018 08:21:15 -0600 - rev 445106
Push 8 by bugmail@asutherland.org at Sat, 11 Aug 2018 16:11:21 +0000
Bug 1425462 Sprinkle some thread safety on the LRU Cache r=handyman We use a mozilla:Mutex to avoid race conditions in the LRU Cache MozReview-Commit-ID: DyeK4RUnGhP
127b5d2e6779a4e94f7e939210a99b12e0c32f5f: Bug 1425462 Normalize the JavaScript Engine behavior by adding a callback r=luke
Tom Ritter <tom@mozilla.com> - Thu, 22 Feb 2018 16:05:50 -0600 - rev 445105
Push 8 by bugmail@asutherland.org at Sat, 11 Aug 2018 16:11:21 +0000
Bug 1425462 Normalize the JavaScript Engine behavior by adding a callback r=luke Time Precision Reduction in the JS Engine was handled by a small bit of duplicated logic. With Time Jittering, and general improvements to the logic due to float fuzziness, we want to unify the logic for the JS Engine and the browser into one location. This patch does that. Note that this will leave the JS Shell without a time jittering implementation. It currently has a time clamping implementation - but I'm not actually sure if the shell is doing anything with it, because it's probably not calling SetTimeResolutionUsec to set it up. In Bug 1440539 we will add a jitter implementation for the shell. (And probably turn time rounding and jittering on for it too.) MozReview-Commit-ID: 2BTIMzE8MjW
95ce64d3a29a9a50de86bf713b69f43b8e05230c: Bug 1425462 Address tests for Time Jittering r=bkelly
Tom Ritter <tom@mozilla.com> - Thu, 15 Feb 2018 15:34:05 -0600 - rev 445104
Push 8 by bugmail@asutherland.org at Sat, 11 Aug 2018 16:11:21 +0000
Bug 1425462 Address tests for Time Jittering r=bkelly The following tests all hardcoded a special value for Timer Precision Reduction. browser/components/extensions/test/xpcshell/test_ext_browsingData_cookies_cache.js browser/components/resistfingerprinting/test/browser/browser_performanceAPI.js browser/components/resistfingerprinting/test/mochitest/test_animation_api.html browser/components/resistfingerprinting/test/mochitest/test_reduce_time_precision.html devtools/client/sourceeditor/test/browser_codemirror.js dom/animation/test/css-animations/test_animation-currenttime.html dom/animation/test/mozilla/test_transition_finish_on_compositor.html dom/media/test/test_video_stats_resistfingerprinting.html dom/tests/mochitest/ajax/jquery/test_jQuery.html netwerk/test/unit/test_race_cache_with_network.js Of these, only test_video_stats_resistfingerprinting.html begins failing when Jitter is enabled. So disable jitter for that test. Additionally, dom/midi/tests/test_midi_packet_timing_sorting.html began failing with Jitter, so we disable it there. (We could easily modify the test so it began passing, but this would reduce the effectiveness of the test.) MozReview-Commit-ID: 2kipxV6wYv9
ddd2c4da4ba4163f8b4cd032feed3bf969cb47ce: Bug 1425462 When reducing the precision of timestamps, also apply fuzzytime to them r=bkelly
Tom Ritter <tom@mozilla.com> - Thu, 01 Mar 2018 00:07:03 -0600 - rev 445103
Push 8 by bugmail@asutherland.org at Sat, 11 Aug 2018 16:11:21 +0000
Bug 1425462 When reducing the precision of timestamps, also apply fuzzytime to them r=bkelly Fuzzytime deterministically generates a random midpoint between two clamped values, and if the unreduced timestamp is above the midpoint, the time is rounded upwards. This allows safe time jittering to occur, as time will never go backwards on a given timeline. It _is_ possible for time to go backwards when comparing different (but related) timelines, such as a relative timeline in one page (with its own performance.timeOrigin) and a relative timeline in an iframe or Worker (which also has its own performance.timeOrigin). This is the same behavior as the 2ms timer reduction we previously landed; jitter doesn't make this any better or worse. MozReview-Commit-ID: IdRLxcWDQBZ
8ac015e407553baf5f4e60fe1e021d8d3f884e1a: Bug 1441153 - Block cross origin redirects after media channel setup for wav. r=jya
Chris Pearce <cpearce@mozilla.com> - Thu, 01 Mar 2018 14:08:30 +1300 - rev 445102
Push 8 by bugmail@asutherland.org at Sat, 11 Aug 2018 16:11:21 +0000
Bug 1441153 - Block cross origin redirects after media channel setup for wav. r=jya
3a5462439ead52afdcee1d2633dcc5426e451d16: Bug 1442037 - Fix an incorrect assert in DecoderFactory::CloneAnimationDecoder. r=tnikkel
Andrew Osmond <aosmond@mozilla.com> - Thu, 01 Mar 2018 19:38:58 -0500 - rev 445101
Push 8 by bugmail@asutherland.org at Sat, 11 Aug 2018 16:11:21 +0000
Bug 1442037 - Fix an incorrect assert in DecoderFactory::CloneAnimationDecoder. r=tnikkel When cloning an animated image decoder, we asserted that Decoder::HasAnimation was true. This is incorrect because if the decoder has yet to complete the metadata decoding, or it has but only finds out the image is animated when it discovers the second frame, then we will try to clone a valid animated image decoder, but fail the assertion. Instead, this patch verifies the image type supports animations.
be154f4de4e9f53e8cdd5363d5a923794cb72174: Backed out changeset cf64879466c4 (bug 1440789) for Android packaging failure
Sebastian Hengst <archaeopteryx@coole-files.de> - Fri, 02 Mar 2018 02:23:11 +0200 - rev 445100
Push 8 by bugmail@asutherland.org at Sat, 11 Aug 2018 16:11:21 +0000
Backed out changeset cf64879466c4 (bug 1440789) for Android packaging failure
5410375734d6ca8be3ff06acdc1c951d87d644ee: Backed out 2 changesets (bug 1428430) for devtools failure on /builds/worker/workspace/build/src/accessible/base/nsAccessibilityService.cpp:1045 a=backout
Dorel Luca <dluca@mozilla.com> - Fri, 02 Mar 2018 01:48:52 +0200 - rev 445099
Push 8 by bugmail@asutherland.org at Sat, 11 Aug 2018 16:11:21 +0000
Backed out 2 changesets (bug 1428430) for devtools failure on /builds/worker/workspace/build/src/accessible/base/nsAccessibilityService.cpp:1045 a=backout Backed out changeset 7d9813d8cb47 (bug 1428430) Backed out changeset a638660a49fa (bug 1428430)
cf64879466c495a47732d9736ef5daa9b35cefc4: Bug 1440789 - Create built_in_addons.json at package-time on mobile r=nalexander
Matthew Finkel <Matthew.Finkel@gmail.com> - Fri, 23 Feb 2018 21:30:51 +0000 - rev 445098
Push 8 by bugmail@asutherland.org at Sat, 11 Aug 2018 16:11:21 +0000
Bug 1440789 - Create built_in_addons.json at package-time on mobile r=nalexander
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip