008043649fc8be854bc15868352403fbc2ba3fc5: Bug 1354499. Disable test_discardAnimatedImage.html temporarily.
Timothy Nikkel <tnikkel@gmail.com> - Sat, 08 Apr 2017 02:04:52 -0500 - rev 558987
Push 52999 by maglione.k@gmail.com at Sat, 08 Apr 2017 20:53:05 +0000
Bug 1354499. Disable test_discardAnimatedImage.html temporarily.
8d01060abf16193158056f3bfa6e22761a2eefa1: Bug 1354499. Do a better job of not recording successful results after test finish in test_discardAnimatedImage.html.
Timothy Nikkel <tnikkel@gmail.com> - Sat, 08 Apr 2017 02:04:52 -0500 - rev 558986
Push 52999 by maglione.k@gmail.com at Sat, 08 Apr 2017 20:53:05 +0000
Bug 1354499. Do a better job of not recording successful results after test finish in test_discardAnimatedImage.html. The previous patch wasn't good enough because it only prevented dispatching more setTimeouts after finish. It did nothing to stop already dispatched setTimeouts from calling ok(true,...).
fc67e6aa71ea7c529bf2b30314410ea847dc7770: Bug 1354499. Don't record further successful results after finishing in test_discardAnimatedImage.html.
Timothy Nikkel <tnikkel@gmail.com> - Fri, 07 Apr 2017 18:26:20 -0500 - rev 558985
Push 52999 by maglione.k@gmail.com at Sat, 08 Apr 2017 20:53:05 +0000
Bug 1354499. Don't record further successful results after finishing in test_discardAnimatedImage.html.
e464cda66cf6d53c3179b14482ae0034863e2dc2: Bug 1354499. Fix test_discardAnimatedImage.html to not call finish multiple times.
Timothy Nikkel <tnikkel@gmail.com> - Fri, 07 Apr 2017 16:11:14 -0500 - rev 558984
Push 52999 by maglione.k@gmail.com at Sat, 08 Apr 2017 20:53:05 +0000
Bug 1354499. Fix test_discardAnimatedImage.html to not call finish multiple times. We can have multiple setTimeouts from multiple frame update notifications in flight at the same time. If one of them reaches the finishing conditions the rest will too. So just guard calling finish with a global bool.
21062cd63dd72565a4f9afc35bb4f6f78726096c: Backed out 2 changesets (bug 1354499) for only changing the failure to a frequent Result logged after SimpleTest.finish()
Phil Ringnalda <philringnalda@gmail.com> - Fri, 07 Apr 2017 21:35:14 -0700 - rev 558983
Push 52999 by maglione.k@gmail.com at Sat, 08 Apr 2017 20:53:05 +0000
Backed out 2 changesets (bug 1354499) for only changing the failure to a frequent Result logged after SimpleTest.finish() CLOSED TREE Backed out changeset 415cd9f87458 (bug 1354499) Backed out changeset 17d681fd2b32 (bug 1354499)
550f156a3c5fa626a693e18ab5584e5a1f6aaed3: Backed out changeset 50aee6c86901 (bug 686905) for not getting its test failure dependency fixed
Phil Ringnalda <philringnalda@gmail.com> - Fri, 07 Apr 2017 21:34:00 -0700 - rev 558982
Push 52999 by maglione.k@gmail.com at Sat, 08 Apr 2017 20:53:05 +0000
Backed out changeset 50aee6c86901 (bug 686905) for not getting its test failure dependency fixed CLOSED TREE
e0bd14f23ac9561cd7ed74bddc24529c8a02b82f: Backed out changeset 35e0a23e1c89 (bug 1346012) for mass crashes in js::IsDeadProxyObject
Phil Ringnalda <philringnalda@gmail.com> - Fri, 07 Apr 2017 20:00:22 -0700 - rev 558981
Push 52999 by maglione.k@gmail.com at Sat, 08 Apr 2017 20:53:05 +0000
Backed out changeset 35e0a23e1c89 (bug 1346012) for mass crashes in js::IsDeadProxyObject CLOSED TREE
b5d165f89e76ef080dde2182f540265b63e8d4a1: Revert "Bug 1349699 - Assert when destroying a MessageLoop that a live MessageChannel is attached to (r=dvander)"
Bill McCloskey <billm@mozilla.com> - Fri, 07 Apr 2017 16:45:02 -0700 - rev 558980
Push 52999 by maglione.k@gmail.com at Sat, 08 Apr 2017 20:53:05 +0000
Revert "Bug 1349699 - Assert when destroying a MessageLoop that a live MessageChannel is attached to (r=dvander)" This reverts commit 9e65608a6214fc500dd4af4822700fd1ad6e000c.
356d65d040d49929e94210d555f3f9fdbbd22fa1: Revert "Bug 1349699 - Assert that the Chromium channel is closed when MessageLoop is destroyed (r=dvander)"
Bill McCloskey <billm@mozilla.com> - Fri, 07 Apr 2017 16:44:59 -0700 - rev 558979
Push 52999 by maglione.k@gmail.com at Sat, 08 Apr 2017 20:53:05 +0000
Revert "Bug 1349699 - Assert that the Chromium channel is closed when MessageLoop is destroyed (r=dvander)" This reverts commit b72a0148dd4a3e633559760c6f0394c851799073.
bb79e576b61769175c0a9d82441d5f73e1c94909: Revert "Bug 1349699 - Close GPU channel unconditionally (r=dvander)"
Bill McCloskey <billm@mozilla.com> - Fri, 07 Apr 2017 16:44:55 -0700 - rev 558978
Push 52999 by maglione.k@gmail.com at Sat, 08 Apr 2017 20:53:05 +0000
Revert "Bug 1349699 - Close GPU channel unconditionally (r=dvander)" This reverts commit acc4397b003ca5a7760ce8bbf24c21df6a2dd8bc.
35e0a23e1c89bc55aa667915d5af41e006c9ed3f: Bug 1346012 - Handle dead object wrappers in more places in Promise code. r=shu
Till Schneidereit <till@tillschneidereit.net> - Fri, 24 Mar 2017 22:49:38 -0700 - rev 558977
Push 52999 by maglione.k@gmail.com at Sat, 08 Apr 2017 20:53:05 +0000
Bug 1346012 - Handle dead object wrappers in more places in Promise code. r=shu MozReview-Commit-ID: HlmKwoMub9D
415cd9f874580ba859372b48bfc690bc13bf3b24: Bug 1354499. Don't record further successful results after finishing in test_discardAnimatedImage.html.
Timothy Nikkel <tnikkel@gmail.com> - Fri, 07 Apr 2017 18:26:20 -0500 - rev 558976
Push 52999 by maglione.k@gmail.com at Sat, 08 Apr 2017 20:53:05 +0000
Bug 1354499. Don't record further successful results after finishing in test_discardAnimatedImage.html.
37d80135ecb58eef37aba5528f271925091b9f07: Bug 1329114 - Update talos symbolication to work with profile format version 5. r?jmaher draft
Markus Stange <mstange@themasta.com> - Sat, 08 Apr 2017 15:06:41 -0400 - rev 558975
Push 52998 by bmo:mstange@themasta.com at Sat, 08 Apr 2017 20:07:55 +0000
Bug 1329114 - Update talos symbolication to work with profile format version 5. r?jmaher MozReview-Commit-ID: K2Hd6pPLaoB
7f4064e8d29261b63619a274804e5174217e4249: Bug 1329114 - Put profiles from other processes into a 'processes' array, not into the threads array, and don't stringify them. r?njn draft
Markus Stange <mstange@themasta.com> - Sat, 08 Apr 2017 16:00:30 -0400 - rev 558974
Push 52998 by bmo:mstange@themasta.com at Sat, 08 Apr 2017 20:07:55 +0000
Bug 1329114 - Put profiles from other processes into a 'processes' array, not into the threads array, and don't stringify them. r?njn MozReview-Commit-ID: Ccl6JIbRMyX
8b4f96095a48906cad2d3d3e560393b2d895939c: Bug 1354842 - Back out bug 1255911 because the subprocess marker time adjustment is now done in perf.html. r?mconley draft
Markus Stange <mstange@themasta.com> - Sat, 08 Apr 2017 15:05:41 -0400 - rev 558973
Push 52997 by bmo:mstange@themasta.com at Sat, 08 Apr 2017 20:05:45 +0000
Bug 1354842 - Back out bug 1255911 because the subprocess marker time adjustment is now done in perf.html. r?mconley MozReview-Commit-ID: 5AhYa4axOJX
31f7dd7c340c279ea61c5234f943b4bd5aff7dce: Bug 1350967 (part 2) - Remove profiler_get_profile_jsobject_async() and profiler_save_profile_to_file_async(). r=mstange. draft
Nicholas Nethercote <nnethercote@mozilla.com> - Wed, 29 Mar 2017 15:48:13 +1100 - rev 558972
Push 52997 by bmo:mstange@themasta.com at Sat, 08 Apr 2017 20:05:45 +0000
Bug 1350967 (part 2) - Remove profiler_get_profile_jsobject_async() and profiler_save_profile_to_file_async(). r=mstange. The state management is better done within nsProfiler::GetProfileDataAsync() and nsProfiler::DumpProfileToFileAsync(). (The latter function is new in this patch.) This fixes a deadlock. Other notes: - The patch moves ProfileGatherer from ProfilerState to nsProfiler. This is nice because the former is shared between threads but the latter is main thread only. (This is how the deadlock is avoided.) - ProfilerStateMutex and PSLockRef are no longer required in platform.h. Those types and variables are now only used in platform.cpp and platform-*.cpp. - ProfilerGatherer now calls profiler_get_profile() instead of ToJSON(). Which means that ToJSON() now has a single caller, so the patch inlines it at the callsite and removes it. - profiler_save_profile_to_file_async() dispatched a Runnable to the main thread. But this wasn't necessary, because it always ran on the main thread itself. So the new function nsProfiler::DumpProfileToFileAsync() doesn't do that. - profiler_will_gather_OOP_profile(), profiler_gathered_OOP_profile(), and profiler_OOP_exit_profile() are all moved into nsProfiler as well. This removes the need for the horrible fake lock in profiler_will_gather_OOP_profile(), hooray! MozReview-Commit-ID: FGpm1KWJ3K1
ec2fc87038bf14c9d011dcf2cba59e63c6aca0c3: Bug 1350967 (part 1) - Remove profiler_get_profile_jsobject. r=mstange. draft
Nicholas Nethercote <nnethercote@mozilla.com> - Tue, 28 Mar 2017 16:01:17 +1100 - rev 558971
Push 52997 by bmo:mstange@themasta.com at Sat, 08 Apr 2017 20:05:45 +0000
Bug 1350967 (part 1) - Remove profiler_get_profile_jsobject. r=mstange. The conversion to a JSObject is better done within nsProfiler::GetProfileData(). MozReview-Commit-ID: CJVEhXuEaiS
ce244cdc57a617129a12df4b7f0ab02c0c893aab: Bug 1351808 - Part 2 - Exclude non-standard tab types from session store. r?sebastian draft
Jan Henning <jh+bugzilla@buttercookie.de> - Sat, 08 Apr 2017 13:43:09 +0200 - rev 558970
Push 52996 by mozilla@buttercookie.de at Sat, 08 Apr 2017 19:59:11 +0000
Bug 1351808 - Part 2 - Exclude non-standard tab types from session store. r?sebastian Restoring anything other than normal browsing tabs (e.g. custom tabs, web apps) is more involved because those tabs - don't appear in our normal tabs UI - are opened in separate activities - when we're starting up, Android's task switcher might or might not still have available task entries corresponding to such tabs from the last session Therefore, for now, the session store will simply exclude those kinds of tabs from being saved in the session store data. Instead of a real restore, if the corresponding tab has been closed or Gecko stopped running, we just recreate the custom tab/web app based on the stored Activity intent data we have available (bug 1352997). Tab zombification while Gecko is running however remains fully supported, as we continue collecting session history data for all tab types, even if we don't necessarily save it to disk. Because custom tabs/web apps currently still share a common Gecko browser window with normal tabs, we also have to modify our selected tab tracking logic accordingly, so that selecting one of these special tab types doesn't overwrite the last selected normal browsing tab. To that effect, we now track the selected tab *ID* in memory and only convert that to a tab index when writing the data to disk. As the ID remains stable while Gecko is running, this makes tracking changes for a sub-group of tabs only easier, as we don't have to watch out for closing tabs of *any* kind affecting the tab index of everything behind them. Bug 1346008#c3 has some preliminary ideas on how session restoring for custom tabs/web apps could be made to work. MozReview-Commit-ID: 1q5Jtv0DKrE
424924e5b78bf3baf5ba9c5feeacb16228ed8fb5: Bug 1351808 - Part 1 - Replace some magic numbers in session store. r?sebastian draft
Jan Henning <jh+bugzilla@buttercookie.de> - Sat, 08 Apr 2017 14:18:23 +0200 - rev 558969
Push 52996 by mozilla@buttercookie.de at Sat, 08 Apr 2017 19:59:11 +0000
Bug 1351808 - Part 1 - Replace some magic numbers in session store. r?sebastian MozReview-Commit-ID: BzqieZVi7h4
7469504bd593bd174db76895fc0f2acb5772e9b5: debug logging draft
Jan Henning <jh+bugzilla@buttercookie.de> - Sat, 08 Apr 2017 19:16:31 +0200 - rev 558968
Push 52996 by mozilla@buttercookie.de at Sat, 08 Apr 2017 19:59:11 +0000
debug logging MozReview-Commit-ID: FoUd4cklLKs
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip