4ec5bc4fff15bf293a7118065df335847d0e2f96: Merge m-c to m-i
Phil Ringnalda <philringnalda@gmail.com> - Thu, 19 Jan 2017 22:12:33 -0800 - rev 377561
Push 1419 by jlund@mozilla.com at Mon, 10 Apr 2017 20:44:07 +0000
Merge m-c to m-i
2b1fcb4b8c8854eea5190c22bdd31c9aca3510f1: Bug 1332353. Make it clearer when a stylesheet is really owned by its mDocument. r=heycam
Boris Zbarsky <bzbarsky@mit.edu> - Thu, 19 Jan 2017 23:49:44 -0500 - rev 377560
Push 1419 by jlund@mozilla.com at Mon, 10 Apr 2017 20:44:07 +0000
Bug 1332353. Make it clearer when a stylesheet is really owned by its mDocument. r=heycam
cdc8e1a140e298a55cff0eedb053bd0155b360f7: Bug 1326442: Use reconfigure whenever possible on video renegotiation r=ng
Randell Jesup <rjesup@jesup.org> - Fri, 30 Dec 2016 10:09:00 -0800 - rev 377559
Push 1419 by jlund@mozilla.com at Mon, 10 Apr 2017 20:44:07 +0000
Bug 1326442: Use reconfigure whenever possible on video renegotiation r=ng
2f514ff474a80a55985ea977bb602b6d8937577d: merge autoland to mozilla-central a=merge
Carsten "Tomcat" Book <cbook@mozilla.com> - Fri, 20 Jan 2017 15:21:47 +0100 - rev 377558
Push 1419 by jlund@mozilla.com at Mon, 10 Apr 2017 20:44:07 +0000
merge autoland to mozilla-central a=merge
516551993d16fb186abb4469ef5eba9f88e91b9b: Bug 1332508 - Reinitialize allocator mutexes in fork() child processes. r=njn
Mike Hommey <mh+mozilla@glandium.org> - Fri, 20 Jan 2017 10:06:41 +0900 - rev 377557
Push 1419 by jlund@mozilla.com at Mon, 10 Apr 2017 20:44:07 +0000
Bug 1332508 - Reinitialize allocator mutexes in fork() child processes. r=njn Adapted from https://github.com/jemalloc/jemalloc/commit/4e2e3dd9cf19ed5991938a708a8b50611aa5bbf8 and https://github.com/jemalloc/jemalloc/commit/d9f7b2a4307f7ff9f7a139b33d366d44e8a8b83d As per the latter commit, it would seem unlocking, in fork() child processes, mutexes that were locked in the parent process is not really well supported on OSX 10.12. The addition of the zone_reinit_lock function in 10.12 supports this idea.
464bdc2b1c2c152438a4fd2456a8908ac5c45ed5: Bug 1286613 - Update jemalloc 4 to c6943ac. r=njn
Mike Hommey <mh+mozilla@glandium.org> - Wed, 18 Jan 2017 15:47:53 +0900 - rev 377556
Push 1419 by jlund@mozilla.com at Mon, 10 Apr 2017 20:44:07 +0000
Bug 1286613 - Update jemalloc 4 to c6943ac. r=njn This picks the same changes as the ones we just did to memory/build/zone.c, plus a oneliner for sparc64.
07cb49de060b9a2a8ab8f4db5e486c50f76bd3a8: Bug 1286613 - Add dummy implementations for most remaining OSX zone allocator functions. r=njn
Mike Hommey <mh+mozilla@glandium.org> - Wed, 18 Jan 2017 14:35:11 +0900 - rev 377555
Push 1419 by jlund@mozilla.com at Mon, 10 Apr 2017 20:44:07 +0000
Bug 1286613 - Add dummy implementations for most remaining OSX zone allocator functions. r=njn Some system libraries are using malloc_default_zone() and then using some of the malloc_zone_* API. Under normal conditions, those functions check the malloc_zone_t/malloc_introspection_t struct for the values that are allowed to be NULL, so that a NULL deref doesn't happen. As of OSX 10.12, malloc_default_zone() doesn't return the actual default zone anymore, but returns a fake, wrapper zone. The wrapper zone defines all the possible functions in the malloc_zone_t/malloc_introspection_t struct (almost), and calls the function from the registered default zone (jemalloc in our case) on its own. Without checking whether the pointers are NULL. This means that a system library that calls e.g. malloc_zone_batch_malloc(malloc_default_zone(), ...) ends up trying to call jemalloc_zone.batch_malloc, which is NULL, and crash follows. So as of OSX 10.12, the default zone is required to have all the functions available (really, the same as the wrapper zone), even if they do nothing. This is arguably a bug in libsystem_malloc in OSX 10.12, but jemalloc still needs to work in that case. [Adapted from https://github.com/jemalloc/jemalloc/commit/c6943acb3c56d1b3d1e82dd43b3fcfeae7771990]
0b74f21e41cda7e9317e756d2e497cf89df369fa: Bug 1286613 - Don't rely on OSX SDK malloc/malloc.h for malloc_zone struct definitions. r=njn
Mike Hommey <mh+mozilla@glandium.org> - Wed, 18 Jan 2017 13:50:35 +0900 - rev 377554
Push 1419 by jlund@mozilla.com at Mon, 10 Apr 2017 20:44:07 +0000
Bug 1286613 - Don't rely on OSX SDK malloc/malloc.h for malloc_zone struct definitions. r=njn The SDK jemalloc is built against might be not be the latest for various reasons, but the resulting binary ought to work on newer versions of OSX. In order to ensure this, we need the fullest definitions possible, so copy what we need from the latest version of malloc/malloc.h available on opensource.apple.com. [Adapted from https://github.com/jemalloc/jemalloc/commit/c68bb4179312665e22d375aecf9f4306607c7c1a]
5cc62bcc4a538cfbea78e60437a5aa0ce542d5ac: Bug 1286613 - Use the same zone allocator implementation as replace-malloc for mozjemalloc. r=njn
Mike Hommey <mh+mozilla@glandium.org> - Wed, 18 Jan 2017 11:45:45 +0900 - rev 377553
Push 1419 by jlund@mozilla.com at Mon, 10 Apr 2017 20:44:07 +0000
Bug 1286613 - Use the same zone allocator implementation as replace-malloc for mozjemalloc. r=njn We have been using a different zone allocator between mozjemalloc and replace-malloc for a long time. Jemalloc 4 uses the same as replace-malloc, albeit as part of the jemalloc upstream code base. We've been bitten many times in the past with Apple changes breaking the zone allocator, and each time we've had to make changes to the three instances, although two of them are similar and the changes there are straightforward. It also turns out that the way the mozjemalloc zone allocator is set up, when a new version of OSX appears with a new version of the system zone allocator, Firefox ends up using the system allocator, because the zone allocator version is not supported. So, we use the same zone allocator for both replace-malloc and mozjemalloc, making everything on par with jemalloc 4.
b5f2e22b254868f124a33057ff58cc2705865c3d: Bug 1286613 - Move replace-malloc zone allocator to a separate file. r=njn
Mike Hommey <mh+mozilla@glandium.org> - Wed, 18 Jan 2017 11:39:29 +0900 - rev 377552
Push 1419 by jlund@mozilla.com at Mon, 10 Apr 2017 20:44:07 +0000
Bug 1286613 - Move replace-malloc zone allocator to a separate file. r=njn The intent here is to reuse the zone allocator for mozjemalloc, to avoid all the shortcomings of mozjemalloc using a different one. This change only moves the replace-malloc zone allocator out of replace-malloc.c, to make changes for mozjemalloc integration clearer.
ee77d1e9cfda6340310a8cac83d952fb25e4137e: Bug 1286613 - Properly call mozjemalloc pre/post fork hooks on OSX when replace-malloc is enabled. r=njn
Mike Hommey <mh+mozilla@glandium.org> - Thu, 19 Jan 2017 09:37:22 +0900 - rev 377551
Push 1419 by jlund@mozilla.com at Mon, 10 Apr 2017 20:44:07 +0000
Bug 1286613 - Properly call mozjemalloc pre/post fork hooks on OSX when replace-malloc is enabled. r=njn Somehow, we never called those hooks when replace-malloc is enabled. I'd expect this to cause random deadlocks when forking, and I'm surprised this hasn't surfaced. Maybe it actually causes some intermittent oranges on automation, who knows. This also brings consistency with what is done for jemalloc 4, and with the mozjemalloc implementation, too, that we're going to replace with this one in a subsequent changeset.
de03a86224cd02af7166f276554122f628504c10: Bug 1331172 - Current permission state should use the past tense. r=Paolo
Dão Gottwald <dao@mozilla.com> - Mon, 16 Jan 2017 20:33:00 +0100 - rev 377550
Push 1419 by jlund@mozilla.com at Mon, 10 Apr 2017 20:44:07 +0000
Bug 1331172 - Current permission state should use the past tense. r=Paolo MozReview-Commit-ID: 7XqHa0xrfsh
ef92919b4acabfb3ffd816a63ff93faa85d2057f: Bug 1311555 - Use filled bookmark star in ActivityStream context menu r=sebastian
Andrzej Hunt <ahunt@mozilla.com> - Wed, 18 Jan 2017 12:20:50 +0100 - rev 377549
Push 1419 by jlund@mozilla.com at Mon, 10 Apr 2017 20:44:07 +0000
Bug 1311555 - Use filled bookmark star in ActivityStream context menu r=sebastian Unfortunately tinting the bookmark star is highly complicated due to the tinting that NavigationView performs (i.e. we'd likely have to disable NavigationView tinting, and do manual tinting on every icon - alternatively we could hack the tint-list to use blue for "checked" items, and set the bookmark item as checked). Since it's unclear if we even want the star to be blue, we'll leave it grey (but filled) for now. MozReview-Commit-ID: DekRZJayKIz
f560f0eef6be10a2e86ba9e5bcbfe6ad911d1969: Bug 1311555 - Pre: remove unused imports r=ahunt
Andrzej Hunt <ahunt@mozilla.com> - Wed, 18 Jan 2017 12:18:06 +0100 - rev 377548
Push 1419 by jlund@mozilla.com at Mon, 10 Apr 2017 20:44:07 +0000
Bug 1311555 - Pre: remove unused imports r=ahunt MozReview-Commit-ID: 6Xk7Z01m41A
17f52807a3169be83050845352d8b27d9eb693e2: Bug 1330986 - Override proguard config to fix VectorDrawable corruption on Android 4 r=sebastian
Andrzej Hunt <ahunt@mozilla.com> - Tue, 17 Jan 2017 12:16:42 +0100 - rev 377547
Push 1419 by jlund@mozilla.com at Mon, 10 Apr 2017 20:44:07 +0000
Bug 1330986 - Override proguard config to fix VectorDrawable corruption on Android 4 r=sebastian See https://code.google.com/p/android/issues/detail?id=209558 . On Devices running Android 4 and below, VectorDrawable's can be corrupted due to overzealous proguarding. This doesn't appear to have been fixed in the support library yet, and even if it were fixed we still wouldn't be able to switch to the most modern support library without significant work. MozReview-Commit-ID: 3ByogGygCEd
d6d0f8b6e78d5913a6414ffd99db30ad4b8cb1e2: Bug 1302027 - enable rust log when MP4Metadata prlog is set. r=kinetik
Alfredo.Yang <ayang@mozilla.com> - Thu, 29 Dec 2016 14:56:34 +0800 - rev 377546
Push 1419 by jlund@mozilla.com at Mon, 10 Apr 2017 20:44:07 +0000
Bug 1302027 - enable rust log when MP4Metadata prlog is set. r=kinetik MozReview-Commit-ID: 7avZ5T4XKDY
f94d77b18a09bd6f9835091280b8acc65a10907d: Backed out changeset cf116f73a2d2 (bug 1330827) for bustage
Iris Hsiao <ihsiao@mozilla.com> - Fri, 20 Jan 2017 15:49:06 +0800 - rev 377545
Push 1419 by jlund@mozilla.com at Mon, 10 Apr 2017 20:44:07 +0000
Backed out changeset cf116f73a2d2 (bug 1330827) for bustage CLOSED TREE
cf116f73a2d29667c763e916003dcba54b55e70e: Bug 1330827 - Fix CSS for Tab's cursor and background; r=jryans
Jan Odvarko <odvarko@gmail.com> - Thu, 19 Jan 2017 13:52:40 +0100 - rev 377544
Push 1419 by jlund@mozilla.com at Mon, 10 Apr 2017 20:44:07 +0000
Bug 1330827 - Fix CSS for Tab's cursor and background; r=jryans MozReview-Commit-ID: GZd51GV3nFP
21e0b0c5284a9f2bad562a79764b0de32be7ec74: Bug 1331431 - Use baseline and FontMetrics instead of textview's center and text size to get the real text height. r=sebastian
Nevin Chen <cnevinchen@gmail.com> - Wed, 18 Jan 2017 17:59:23 +0800 - rev 377543
Push 1419 by jlund@mozilla.com at Mon, 10 Apr 2017 20:44:07 +0000
Bug 1331431 - Use baseline and FontMetrics instead of textview's center and text size to get the real text height. r=sebastian MozReview-Commit-ID: 4HJKZP0F0ow
8bfeb8f4a4f5f63b220e18ee817f90281ef4c242: Bug 1275662 - Close all tabs and clean up session files when "Open Tabs" is selected in "Clear private data on exit" or "Clear private data" pref. r=JanH,sebastian
Nevin Chen <cnevinchen@gmail.com> - Thu, 29 Dec 2016 14:22:45 +0800 - rev 377542
Push 1419 by jlund@mozilla.com at Mon, 10 Apr 2017 20:44:07 +0000
Bug 1275662 - Close all tabs and clean up session files when "Open Tabs" is selected in "Clear private data on exit" or "Clear private data" pref. r=JanH,sebastian MozReview-Commit-ID: GoUQVDIzYbI
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip