320642944e42a889db13c6c55b404e32319d4de6: Backed out changeset 548ed79f2337 (bug 1053321) for strange and terribly-reported failures in Android opt mochitest-15 and debug mochitest-36 FIREFOX_BETA_56_BASE
Phil Ringnalda <philringnalda@gmail.com> - Tue, 01 Aug 2017 23:13:42 -0700 - rev 619569
Push 71721 by bmo:fliu@mozilla.com at Wed, 02 Aug 2017 08:10:12 +0000
Backed out changeset 548ed79f2337 (bug 1053321) for strange and terribly-reported failures in Android opt mochitest-15 and debug mochitest-36 CLOSED TREE MozReview-Commit-ID: IigWQ1wnxhZ
6116c78db606182446bf0d3b1034f882f6739155: Bug 1385783 - Insert the elfhack code before the first executable section. r?froydnj draft
Mike Hommey <mh+mozilla@glandium.org> - Wed, 02 Aug 2017 16:39:12 +0900 - rev 619568
Push 71720 by bmo:mh+mozilla@glandium.org at Wed, 02 Aug 2017 07:44:07 +0000
Bug 1385783 - Insert the elfhack code before the first executable section. r?froydnj The lld linker creates separate segments for purely executable sections (such as .text) and sections preceding those (such as .rel.dyn). Neither gold nor bfd ld do that, and just put all those sections in the same executable segment. Since elfhack is putting its executable code between the two relocation sections, it ends up in a non-executable segment, leading to a crash when it's time to run that code. We thus insert the elfhack code before the first executable section instead of between the two relocation sections (which is where the elfhack data lies, and stays).
4ed816d4f98a07ca07c4e6c0421b7269d7df69bc: Bug 1385783 - Don't assume both elfhack sections are next to each other. r?froydnj draft
Mike Hommey <mh+mozilla@glandium.org> - Wed, 02 Aug 2017 16:05:07 +0900 - rev 619567
Push 71720 by bmo:mh+mozilla@glandium.org at Wed, 02 Aug 2017 07:44:07 +0000
Bug 1385783 - Don't assume both elfhack sections are next to each other. r?froydnj
5a787f09ddeded2f3097a995f267fbce8d88d493: Bug 1385929 - Part 2. Remove unecessary gfxContext::Save/Restore found by Part 1. draft
cku <cku@mozilla.com> - Tue, 01 Aug 2017 20:38:15 +0800 - rev 619566
Push 71719 by bmo:cku@mozilla.com at Wed, 02 Aug 2017 07:36:27 +0000
Bug 1385929 - Part 2. Remove unecessary gfxContext::Save/Restore found by Part 1. gfxContext::PushGroupAndCopyBackground & PushGroupForBlendBack do not change the content of AzureState, we should remove gfxContext::Save in these two functions. MozReview-Commit-ID: LUuC7bkqFba
e24c2a3a98c6243c974a30f1eeb80322f0d4b7d9: Bug 1385929 - Part 1. Check whether the content of the persisted state change. draft
cku <cku@mozilla.com> - Tue, 01 Aug 2017 16:33:08 +0800 - rev 619565
Push 71719 by bmo:cku@mozilla.com at Wed, 02 Aug 2017 07:36:27 +0000
Bug 1385929 - Part 1. Check whether the content of the persisted state change. Since gfxContext::Save keep appear on my screen when I did profile, so I think we should find a way to prevent unecessary usage of this function. By this patch, an assertion message will be dump if we save and restore an unchanged AzureState. MozReview-Commit-ID: 5lH1Y5T5K7t
39b8046493b4f65341cb101ee296f23f4016ba7c: Bug 1385929 - Part 2. Remove unecessary gfxContext::Save/Restore found by Part 1. draft
cku <cku@mozilla.com> - Tue, 01 Aug 2017 20:38:15 +0800 - rev 619564
Push 71718 by bmo:cku@mozilla.com at Wed, 02 Aug 2017 07:31:51 +0000
Bug 1385929 - Part 2. Remove unecessary gfxContext::Save/Restore found by Part 1. gfxContext::PushGroupAndCopyBackground & PushGroupForBlendBack do not change the content of AzureState, we should remove gfxContext::Save in these two functions. MozReview-Commit-ID: LUuC7bkqFba
4cb18f569614c8461a863a73e0a96fb9b6801aa6: Bug 1385929 - Part 1. Check whether the content of the persisted state change. draft
cku <cku@mozilla.com> - Tue, 01 Aug 2017 16:33:08 +0800 - rev 619563
Push 71718 by bmo:cku@mozilla.com at Wed, 02 Aug 2017 07:31:51 +0000
Bug 1385929 - Part 1. Check whether the content of the persisted state change. Since gfxContext::Save keep appear on my screen when I did profile, so I think we should find a way to prevent unecessary usage of this function. By this patch, an assertion message will be dump if we save and restore an unchanged AzureState. MozReview-Commit-ID: 5lH1Y5T5K7t
66ea98cdd7195b8206ce7b62e4bc6ee40feb37a3: Bug 1385929 - Part 2. Remove unecessary gfxContext::Save/Restore found by Part 1. draft
cku <cku@mozilla.com> - Tue, 01 Aug 2017 20:38:15 +0800 - rev 619562
Push 71717 by bmo:cku@mozilla.com at Wed, 02 Aug 2017 07:16:19 +0000
Bug 1385929 - Part 2. Remove unecessary gfxContext::Save/Restore found by Part 1. gfxContext::PushGroupAndCopyBackground & PushGroupForBlendBack do not change the content of AzureState, we should remove gfxContext::Save in these two functions. MozReview-Commit-ID: LUuC7bkqFba
4ab191216c44e77bd7ef7475f1ea6cb3cde914ce: Bug 1385929 - Part 1. Check whether the content of the persisted state change. draft
cku <cku@mozilla.com> - Tue, 01 Aug 2017 16:33:08 +0800 - rev 619561
Push 71717 by bmo:cku@mozilla.com at Wed, 02 Aug 2017 07:16:19 +0000
Bug 1385929 - Part 1. Check whether the content of the persisted state change. Since gfxContext::Save keep appear when I did profile, so I think we should have a mechanism to detect unecessary usage of this function. By this patch, gecko will dump an assertion message if it notice we save and restore an unchanged AzureState. MozReview-Commit-ID: 5lH1Y5T5K7t
2f3271576996dbfcce2c6499a2016339b304131f: Bug 1385929 - Part 2. Remove unecessary gfxContext::Save/Restore found by Part 1. draft
cku <cku@mozilla.com> - Tue, 01 Aug 2017 20:38:15 +0800 - rev 619560
Push 71716 by bmo:cku@mozilla.com at Wed, 02 Aug 2017 07:07:11 +0000
Bug 1385929 - Part 2. Remove unecessary gfxContext::Save/Restore found by Part 1. gfxContext::PushGroupAndCopyBackground & PushGroupForBlendBack do not change the content of AzureState, we should remove gfxContext::Save in these two functions. MozReview-Commit-ID: LUuC7bkqFba
ce7aa4258091b2ec630b3fd29f065f41292524fd: Bug 1385929 - Part 1. Check whether the content of the persisted state change. draft
cku <cku@mozilla.com> - Tue, 01 Aug 2017 16:33:08 +0800 - rev 619559
Push 71716 by bmo:cku@mozilla.com at Wed, 02 Aug 2017 07:07:11 +0000
Bug 1385929 - Part 1. Check whether the content of the persisted state change. MozReview-Commit-ID: 5lH1Y5T5K7t
689248dbd4a4add1ca228c5399f70e444a431b3b: Bug 1382579 - Part 3: Tests, r=gijs draft
Fischer Liu<fliu@mozilla.com> - Wed, 02 Aug 2017 13:53:05 +0800 - rev 619558
Push 71715 by fliu@mozilla.com at Wed, 02 Aug 2017 07:02:24 +0000
Bug 1382579 - Part 3: Tests, r=gijs This commit - adds 2 utility functions to the uitour's head.js - adds the browser_UITour4.js - moves the tests in the browser_showMenu_controlCenter.js into the newly added the browser_showMenu.js - deletes the browser_showMenu_urlbar.js because it's test has been modified and moved into the browser_showMenu.js - adds one test case for the page action panel in the browser_showMenu.js - updates the browser_UITour_availableTargets.js test because we have more targets right now. MozReview-Commit-ID: CydEAkqAl3V
c8d842c2f2c84d6cbdd0858d38cebd134e739005: Bug 1373206 - Create a new dialog for notification settings under Firefox Preferences to match the new spec. r?johannh draft
Prathiksha <prathikshaprasadsuman@gmail.com> - Thu, 29 Jun 2017 23:49:35 +0530 - rev 619557
Push 71714 by bmo:prathikshaprasadsuman@gmail.com at Wed, 02 Aug 2017 07:00:40 +0000
Bug 1373206 - Create a new dialog for notification settings under Firefox Preferences to match the new spec. r?johannh MozReview-Commit-ID: 5RUOLPfC2Hk
a09c71739e961d58f580e89a976506c78027694e: Bug 1369309 - Part 4: Modify the test case 'test_video_stats_resistfingerprinting.html'. r?cpearce,arthuredelstein draft
Tim Huang <tihuang@mozilla.com> - Mon, 17 Jul 2017 17:30:08 +0800 - rev 619556
Push 71713 by bmo:tihuang@mozilla.com at Wed, 02 Aug 2017 06:55:21 +0000
Bug 1369309 - Part 4: Modify the test case 'test_video_stats_resistfingerprinting.html'. r?cpearce,arthuredelstein This patch modifies the test case 'test_video_stats_resistfingerprinting.html' to check media statistics report spoofed values when fingerprinting resistance is enabled. This test will play a video and test the media statistics when the video is finished. It will make sure all media statistics report correct spoofed values corresponding to the play time of the video. MozReview-Commit-ID: GpYewu7cIbY
9b5869c4e331eb7fb85168d49754a4706e92f8a6: Bug 1369309 - Part 3: Making the media statistics reports a spoofed value when fingerprinting resistance is enabled. r?cpearce,arthuredelstein draft
Tim Huang <tihuang@mozilla.com> - Mon, 17 Jul 2017 15:13:55 +0800 - rev 619555
Push 71713 by bmo:tihuang@mozilla.com at Wed, 02 Aug 2017 06:55:21 +0000
Bug 1369309 - Part 3: Making the media statistics reports a spoofed value when fingerprinting resistance is enabled. r?cpearce,arthuredelstein This patch makes the media statistics report values with a fixed frames per second and a dynamic dropped ratio when resistance fingerprinting is enabled. The dropped rate is decided by the video resolution that it will report a fixed dropped rate when the video resolution is greater than 480p. And It will report a zero dropped rate if the video is below or equal to 480p. In addition, it adds three new prefs that allow us to change the value of frames per second, the dropped ratio and the threshold of target video resolution. The three prefs are 'privacy.resistFingerprinting.video_frames_per_sec', 'privacy.resistFingerprinting.video_dropped_ratio' and 'privacy.resistFingerprinting.target_video_res'. The default values of them are 30, 5 and 480, which means 30 frames per second, 5 percent dropped ratio and 480p. This also adds a new helper function 'nsContentUtils::ShouldResistFingerprinting(nsIDocument* aDoc)' for checking whether fingerprinting resistance is enabled for a given docuemnt. If it is a chrome document, this function will indicate that fingerprinting resistance is not enabled regardless of the pref 'privacy.resistFingerprinting'. If it is a content document, the result will depend on the pref. MozReview-Commit-ID: FbSuRq6Zdnn
87dfdb80278d307695d5d713dd560dcf1bf418d8: Bug 1369309 - Part 4: Modify the test case 'test_video_stats_resistfingerprinting.html'. r?cpearce,arthuredelstein draft
Tim Huang <tihuang@mozilla.com> - Mon, 17 Jul 2017 17:30:08 +0800 - rev 619554
Push 71712 by bmo:tihuang@mozilla.com at Wed, 02 Aug 2017 06:50:27 +0000
Bug 1369309 - Part 4: Modify the test case 'test_video_stats_resistfingerprinting.html'. r?cpearce,arthuredelstein This patch modifies the test case 'test_video_stats_resistfingerprinting.html' to check media statistics report spoofed values when fingerprinting resistance is enabled. This test will play a video and test the media statistics when the video is finished. It will make sure all media statistics report correct spoofed values corresponding to the play time of the video. MozReview-Commit-ID: GpYewu7cIbY
c29060cae9fbc6f0660b8cf1eb8f781f67489915: Bug 1369309 - Part 3: Making the media statistics reports a spoofed value when fingerprinting resistance is enabled. r?cpearce,arthuredelstein draft
Tim Huang <tihuang@mozilla.com> - Mon, 17 Jul 2017 15:13:55 +0800 - rev 619553
Push 71712 by bmo:tihuang@mozilla.com at Wed, 02 Aug 2017 06:50:27 +0000
Bug 1369309 - Part 3: Making the media statistics reports a spoofed value when fingerprinting resistance is enabled. r?cpearce,arthuredelstein This patch makes the media statistics report values with a fixed frames per second and a dynamic dropped ratio when resistance fingerprinting is enabled. The dropped rate is decided by the video resolution that it will report a fixed dropped rate when the video resolution is greater than 480p. And It will report a zero dropped rate if the video is below or equal to 480p. In addition, it adds three new prefs that allow us to change the value of frames per second, the dropped ratio and the threshold of target video resolution. The three prefs are 'privacy.resistFingerprinting.video_frames_per_sec', 'privacy.resistFingerprinting.video_dropped_ratio' and 'privacy.resistFingerprinting.target_video_res'. The default values of them are 30, 5 and 480, which means 30 frames per second, 5 percent dropped ratio and 480p. This also adds a new helper function 'nsContentUtils::ShouldResistFingerprinting(nsIDocument* aDoc)' for checking whether fingerprinting resistance is enabled for a given docuemnt. If it is a chrome document, this function will indicate that fingerprinting resistance is not enabled regardless of the pref 'privacy.resistFingerprinting'. If it is a content document, the result will depend on the pref. MozReview-Commit-ID: FbSuRq6Zdnn
214f8c66f73711d7491271833db0a66c1ed155bf: Bug 1369309 - Part 2: Add a test case to check whether media statistics has been spoofed correctly when 'privacy.resistFingerprinting' is true. r?jwwang,arthuredelstein draft
Tim Huang <tihuang@mozilla.com> - Mon, 19 Jun 2017 14:43:27 +0800 - rev 619552
Push 71712 by bmo:tihuang@mozilla.com at Wed, 02 Aug 2017 06:50:27 +0000
Bug 1369309 - Part 2: Add a test case to check whether media statistics has been spoofed correctly when 'privacy.resistFingerprinting' is true. r?jwwang,arthuredelstein MozReview-Commit-ID: F6jNk58z7bH
44f972111213118864e4490cd20ad8410a8fb5d6: Bug 1369309 - Part 1: Spoofing media statistics to 0 when 'privacy.resistFingerprinting' is true. r?jwwang,arthuredelstein draft
Tim Huang <tihuang@mozilla.com> - Mon, 19 Jun 2017 14:43:26 +0800 - rev 619551
Push 71712 by bmo:tihuang@mozilla.com at Wed, 02 Aug 2017 06:50:27 +0000
Bug 1369309 - Part 1: Spoofing media statistics to 0 when 'privacy.resistFingerprinting' is true. r?jwwang,arthuredelstein MozReview-Commit-ID: FNALpUGFDTQ
73b38c640ad3e3fbcfa86088ae62309386605bb0: Bug 1385144 - Overlapping negative line numbers do not display as a stack. r?zer0 draft
Micah Tigley <tigleym@gmail.com> - Mon, 31 Jul 2017 21:55:00 -0600 - rev 619550
Push 71711 by bmo:tigleym@gmail.com at Wed, 02 Aug 2017 06:46:24 +0000
Bug 1385144 - Overlapping negative line numbers do not display as a stack. r?zer0 MozReview-Commit-ID: xlkj6OjL4n
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip