Bug 1335148 - Part 2: Introduce notification for end of memory pressure. r=gsvelto,snorp For Fennec on Android, if we haven't received memory pressure notifications from the OS for a certain amount of time (in the order of ~15 mins), we assume that we're no longer under memory pressure. In order to turn the bfcache back on when that happens, we now want to be able to forward this fact to Gecko as well. Unfortunately, the way memory pressure is tracked using an atomic variable doesn't easily allow to fully extend the existing priority rules between "new" and "ongoing" to include a new "stopping of memory pressure" event. Since we're not using Dispatch*Eventual*MemoryPressure on Android and therefore the queuing priority behaviour isn't actually relevant for us, we just ignore that and only enforce that a pending "new" memory pressure event takes priority over a "stop" event. MozReview-Commit-ID: 90C9KogUyvf

Bug 1335148 - Part 1: Dynamically determine content viewer count on Android, too. r=bz,snorp The current limit of at most one bfcache entry on Android dates back to when Fennec was built for the Nokia N810, which had a whopping 128 MB of memory. Since a few years have passed since then and mobile device technology has evolved considerably, it should be safe now to allow a little more than that. Since web sites sizes might have grown somewhat as well compared to the figure of 4MB mentioned in CalcMaxTotalViweres(), though and to be absolutely on the safe side, we still tweak the formula when building for Android, though. If in the worst case even those assumptions turn out too generous, we will still be protected by the fact that - we temporarily disable the bfcache when the OS signals memory pressure, and - our contentViewerTimeout is set to a lower value than on Desktop, so bfcache entries will expire sooner MozReview-Commit-ID: 1A6d0Q6Mdx0

Bug 739219 - Remove nsIBrowserHistory. r=standard8 MozReview-Commit-ID: G1n44eSFWr1

Bug 1459243 - Always store last check pref in RemoteSettings r=mgoodwin MozReview-Commit-ID: 2CvYBKoOOaE

Merge mozilla-central to autoland. a=merge CLOSED TREE

Bug 1460116 - Remove ShouldHideScrollbars. r=jimm MozReview-Commit-ID: 7v6Eylefk4t

Bug 1453788 - Allow top level HTML windows to have persistent window state. r=smaug Move tracking of persistent window state into nsXULWindow. Also, move special handling of the width/height of the window into nsXULWindow. MozReview-Commit-ID: LOmHGyYeNSU

Bug 1460385 - Don't trace propid in TraceCycleCollectorChildren. r=sfink The propid is a jsid, and a jsid can never be anything the CC cares about, so there's no reason to trace it. In at least one profile of Google Inbox, tracing shape propids is taking the majority of time in the CC and causing very long pauses. MozReview-Commit-ID: HcjnawBHLx1

Bug 1459297 - Use SDK JNI calls for boxing/unboxing GeckoBundle values; r=snorp Instead of the helper methods in GeckoBundle, add SDK JNI calls for the boxing/unboxing operations, and use those calls directly. Moreover, for unboxing Boolean/Double/Integer, use their internal "value" field value directly if possible, to avoid making a JNI method call. MozReview-Commit-ID: Azvov1gCeje

Bug 1459298 - Stop spinning event loop when window closes; r=esawin If our window closes while we're spinning the event loop, stop spinning as soon as possible so we can continue with cleaning up the window. MozReview-Commit-ID: ByS0c6R0cM8

Bug 1455872 - Build support for the new raptor performance framework; r=gps MozReview-Commit-ID: FBvXwkYfz0o

Bug 1455872 - Raptor fixes for production; r=ahal MozReview-Commit-ID: KVqypuqHjF9

Bug 1455872 - Add taskcluster configs for raptor on OSX; r=jmaher MozReview-Commit-ID: I67InZTEziy

bug 1460312 - cancel the timeout timer in OCSP request implementation r=jcj Bug 1456489 cleaned up our OCSP request implementation a bit. One simplification it made was to not cancel the timeout timer. It turns out that if we don't, the OCSPRequest that constitutes the timeout callback's closure might not be valid if the request has completed (because the timer doesn't own a strong reference to it). The fix is simple: cancel the timer when the request completes. Note that we don't have to do the reverse because necko has a strong reference to the request. MozReview-Commit-ID: 2WHFLAcGBAw

bug 1460350 - re-land bug 1415991 (remove support for verifying signed unpacked add-ons) r=kmag (Backed out changeset 6bbf8dc0b86e (which was a backout of changeset 0a5795108e0a)) MozReview-Commit-ID: EZFn7dLBcdh

Bug 1459066 - Overflow menu WebExtension subview header should use the default browser styling instead of the extension's styling. r=mixedpuppy MozReview-Commit-ID: EtQ6VS5OH0e

Bug 1457021 - Add l10n migration script for Preferences Subdialog migration to Fluent. r=flod MozReview-Commit-ID: 4Uzmbb08f8K

Bug 1457021 - Fix a mangled message ID order in a Preferences::Permissions JS dialog. r=Gijs MozReview-Commit-ID: JeAxaSTWllA

Bug 1457021 - Migrate the JS of Preferences::SitePermissions to Fluent. r=flod,jaws MozReview-Commit-ID: Fe4Q6CnTcuj

Bug 1457021 - Migrate the JS of Preferences::Translation to Fluent. r=Gijs MozReview-Commit-ID: 8UTYUyOvnBz