e990276c99353565f3e57f0c9495378c5b482f19: Added THUNDERBIRD_52_0b3_RELEASE THUNDERBIRD_52_0b3_BUILD1 tag(s) for changeset a73b7f5955b2. DONTBUILD CLOSED TREE a=release THUNDERBIRD520b3_2017021511_RELBRANCH
tbirdbld - Wed, 15 Feb 2017 11:27:52 -0500 - rev 367122
Push 6934 by tbirdbld at Wed, 15 Feb 2017 16:27:59 +0000
Added THUNDERBIRD_52_0b3_RELEASE THUNDERBIRD_52_0b3_BUILD1 tag(s) for changeset a73b7f5955b2. DONTBUILD CLOSED TREE a=release
a73b7f5955b2369745213bde42d315ee4af31b12: Automated checkin: version bump for thunderbird 52.0b3 release. DONTBUILD CLOSED TREE a=release THUNDERBIRD520b3_2017021511_RELBRANCH THUNDERBIRD_52_0b3_BUILD1 THUNDERBIRD_52_0b3_RELEASE
tbirdbld - Wed, 15 Feb 2017 11:27:49 -0500 - rev 367121
Push 6934 by tbirdbld at Wed, 15 Feb 2017 16:27:59 +0000
Automated checkin: version bump for thunderbird 52.0b3 release. DONTBUILD CLOSED TREE a=release
83856b479b9a29e49e80ff42c1227c84a9a3e086: Bug 1332508 - Reinitialize allocator mutexes in fork() child processes. r=njn a=jorgk DONTBUILD THUNDERBIRD520b3_2017021501_RELBRANCH
Mike Hommey <mh+mozilla@glandium.org> - Fri, 20 Jan 2017 10:06:41 +0900 - rev 367120
Push 6933 by mozilla@jorgk.com at Wed, 15 Feb 2017 14:33:25 +0000
Bug 1332508 - Reinitialize allocator mutexes in fork() child processes. r=njn a=jorgk DONTBUILD 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.
b65cb0c58fdfb56fd77cd6c0775910d3148c9769: Bug 1286613 - Update jemalloc 4 to c6943ac. r=njn a=jorgk THUNDERBIRD520b3_2017021501_RELBRANCH
Mike Hommey <mh+mozilla@glandium.org> - Wed, 18 Jan 2017 15:47:53 +0900 - rev 367119
Push 6933 by mozilla@jorgk.com at Wed, 15 Feb 2017 14:33:25 +0000
Bug 1286613 - Update jemalloc 4 to c6943ac. r=njn a=jorgk This picks the same changes as the ones we just did to memory/build/zone.c, plus a oneliner for sparc64.
42c68421c0844c74f947675fc9006844edaeb6ed: Bug 1286613 - Add dummy implementations for most remaining OSX zone allocator functions. r=njn a=jorgk THUNDERBIRD520b3_2017021501_RELBRANCH
Mike Hommey <mh+mozilla@glandium.org> - Wed, 18 Jan 2017 14:35:11 +0900 - rev 367118
Push 6933 by mozilla@jorgk.com at Wed, 15 Feb 2017 14:33:25 +0000
Bug 1286613 - Add dummy implementations for most remaining OSX zone allocator functions. r=njn a=jorgk 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]
c167ab84f6087db0571429062012e9532e5fbac0: Bug 1286613 - Don't rely on OSX SDK malloc/malloc.h for malloc_zone struct definitions. r=njn a=jorgk THUNDERBIRD520b3_2017021501_RELBRANCH
Mike Hommey <mh+mozilla@glandium.org> - Wed, 18 Jan 2017 13:50:35 +0900 - rev 367117
Push 6933 by mozilla@jorgk.com at Wed, 15 Feb 2017 14:33:25 +0000
Bug 1286613 - Don't rely on OSX SDK malloc/malloc.h for malloc_zone struct definitions. r=njn a=jorgk 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]
5cfc35d102ae0bc4a2268139292e83a0cd827ea6: Bug 1286613 - Use the same zone allocator implementation as replace-malloc for mozjemalloc. r=njn a=jorgk THUNDERBIRD520b3_2017021501_RELBRANCH
Mike Hommey <mh+mozilla@glandium.org> - Wed, 18 Jan 2017 11:45:45 +0900 - rev 367116
Push 6933 by mozilla@jorgk.com at Wed, 15 Feb 2017 14:33:25 +0000
Bug 1286613 - Use the same zone allocator implementation as replace-malloc for mozjemalloc. r=njn a=jorgk 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.
f70c4c3941b199481dae7e51ce55f1b9102e04fc: Bug 1286613 - Move replace-malloc zone allocator to a separate file. r=njn a=jorgk THUNDERBIRD520b3_2017021501_RELBRANCH
Mike Hommey <mh+mozilla@glandium.org> - Wed, 18 Jan 2017 11:39:29 +0900 - rev 367115
Push 6933 by mozilla@jorgk.com at Wed, 15 Feb 2017 14:33:25 +0000
Bug 1286613 - Move replace-malloc zone allocator to a separate file. r=njn a=jorgk 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.
b76377c0399b2680450d570d670f9bf70105bafe: Bug 1286613 - Properly call mozjemalloc pre/post fork hooks on OSX when replace-malloc is enabled. r=njn a=jorgk THUNDERBIRD520b3_2017021501_RELBRANCH
Mike Hommey <mh+mozilla@glandium.org> - Thu, 19 Jan 2017 09:37:22 +0900 - rev 367114
Push 6933 by mozilla@jorgk.com at Wed, 15 Feb 2017 14:33:25 +0000
Bug 1286613 - Properly call mozjemalloc pre/post fork hooks on OSX when replace-malloc is enabled. r=njn a=jorgk 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.
8e6231d2b82e0e7cd5a21c6cd516963b4a8aa298: Bug 1275204 - mozjemalloc: Use the JS arm64 allocator on Linux/sparc64. r=glandium a=jorgk THUNDERBIRD520b3_2017021501_RELBRANCH
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> - Mon, 12 Dec 2016 17:35:15 +0100 - rev 367113
Push 6933 by mozilla@jorgk.com at Wed, 15 Feb 2017 14:33:25 +0000
Bug 1275204 - mozjemalloc: Use the JS arm64 allocator on Linux/sparc64. r=glandium a=jorgk
f87031603d732aa84a32409a0d50fd09064a8b89: Bug 1275204 - mozjemalloc: Use better pre-processor defines for sparc64. r=glandium a=jorgk THUNDERBIRD520b3_2017021501_RELBRANCH
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> - Mon, 12 Dec 2016 17:31:34 +0100 - rev 367112
Push 6933 by mozilla@jorgk.com at Wed, 15 Feb 2017 14:33:25 +0000
Bug 1275204 - mozjemalloc: Use better pre-processor defines for sparc64. r=glandium a=jorgk
339db4c6bec0f0b21e4ad443e95364ce80e46c05: Bug 1311039 - Properly detect the default malloc zone on OSX 10.12. r=njn a=jorgk THUNDERBIRD520b3_2017021501_RELBRANCH
Mike Hommey <mh+mozilla@glandium.org> - Thu, 03 Nov 2016 10:02:06 +0900 - rev 367111
Push 6933 by mozilla@jorgk.com at Wed, 15 Feb 2017 14:33:25 +0000
Bug 1311039 - Properly detect the default malloc zone on OSX 10.12. r=njn a=jorgk
6b15a1c1b523a4c26f9ffd9a0ee224b7ee281a64: Bug 1322027 - Don't disable hugepage support since it no longer causes PGO issues. a=jorgk THUNDERBIRD520b3_2017021501_RELBRANCH
Ryan VanderMeulen <ryanvm@gmail.com> - Wed, 11 Jan 2017 09:04:48 -0500 - rev 367110
Push 6933 by mozilla@jorgk.com at Wed, 15 Feb 2017 14:33:25 +0000
Bug 1322027 - Don't disable hugepage support since it no longer causes PGO issues. a=jorgk
2de37a3fe26522d1ffe690328b739b91bb4babb8: Bug 1322027 - Update jemalloc 4 to version 4.4.0. r=glandium a=jorgk THUNDERBIRD520b3_2017021501_RELBRANCH
Ryan VanderMeulen <ryanvm@gmail.com> - Tue, 10 Jan 2017 22:50:36 -0500 - rev 367109
Push 6933 by mozilla@jorgk.com at Wed, 15 Feb 2017 14:33:25 +0000
Bug 1322027 - Update jemalloc 4 to version 4.4.0. r=glandium a=jorgk
5e8f82a565cfe536feb9bb3a6b16395eaf14bf40: Bug 1339438 - Fix the test that checks that MediaElementAudioSourceNode are working correctly. r=pehrsons a=test-only
Paul Adenot <paul@paul.cx> - Tue, 14 Feb 2017 19:28:04 +0100 - rev 367108
Push 6932 by paul@paul.cx at Wed, 15 Feb 2017 12:50:48 +0000
Bug 1339438 - Fix the test that checks that MediaElementAudioSourceNode are working correctly. r=pehrsons a=test-only MozReview-Commit-ID: Fazp4QsbxHk
bcb00c291057912faded2a802c72d01c9cb1e76d: Bug 1325707 - Change IPC_OK() to true to fix bustage in VideoDecoderParent.cpp. a=bustage
Ryan VanderMeulen <ryanvm@gmail.com> - Tue, 14 Feb 2017 15:45:16 -0500 - rev 367107
Push 6931 by ryanvm@gmail.com at Tue, 14 Feb 2017 20:45:39 +0000
Bug 1325707 - Change IPC_OK() to true to fix bustage in VideoDecoderParent.cpp. a=bustage
d2d15b1d60525688a744450736174f24dfe7794d: Bug 1325707: P2. Handle OOM conditions when creating MediaRawData object. r=gerald, a=jcristau
Jean-Yves Avenard <jyavenard@mozilla.com> - Tue, 07 Feb 2017 09:03:36 +0100 - rev 367106
Push 6930 by jyavenard@mozilla.com at Tue, 14 Feb 2017 20:27:27 +0000
Bug 1325707: P2. Handle OOM conditions when creating MediaRawData object. r=gerald, a=jcristau MozReview-Commit-ID: HtkhrT36Kf4
52f1268d8868d8295865c9fa12600c1dad3798e8: Bug 1325707: P1. Check returned value. r=gerald, a=jcristau
Jean-Yves Avenard <jyavenard@mozilla.com> - Tue, 07 Feb 2017 08:55:28 +0100 - rev 367105
Push 6930 by jyavenard@mozilla.com at Tue, 14 Feb 2017 20:27:27 +0000
Bug 1325707: P1. Check returned value. r=gerald, a=jcristau This is really just for cleanliness perspective, as it can never happen, we always check that demuxing a packet succeeded first. MozReview-Commit-ID: FQ1yz16m9Ix
97ce4f0843b9aa1288ddf3553efe1d0c2fd8c6a4: Bug 1335854 - Tone down non-zero refcount message for dynamic atoms. r=froydnj, a=jcristau
Jorg K <jorgk@jorgk.com> - Wed, 01 Feb 2017 11:47:00 -0500 - rev 367104
Push 6929 by ryanvm@gmail.com at Tue, 14 Feb 2017 18:31:07 +0000
Bug 1335854 - Tone down non-zero refcount message for dynamic atoms. r=froydnj, a=jcristau
49f969a728e99b3cc3bc8759c226e93a34b9b08b: Bug 1276669 - Part 11: Strengthen assertions for atom table shutdown GC. r=erahm, a=jcristau
Nathan Froyd <froydnj@mozilla.com> - Thu, 26 Jan 2017 16:43:38 -0400 - rev 367103
Push 6929 by ryanvm@gmail.com at Tue, 14 Feb 2017 18:31:07 +0000
Bug 1276669 - Part 11: Strengthen assertions for atom table shutdown GC. r=erahm, a=jcristau This could have been done more simply, but the small amount of refactoring that takes place in this comment enables better error messages in the case where something does go wrong.
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip