Closed Bug 1343432 Opened 3 years ago Closed 3 years ago
Update jemalloc 4 to version 4
https://github.com/jemalloc/jemalloc/releases/tag/4.5.0 * 4.5.0 (February 28, 2017) This is the first release to benefit from much broader continuous integration testing, thanks to @davidtgoldblatt. Had we had this testing infrastructure in place for prior releases, it would have caught all of the most serious regressions fixed by this release. New features: - Add --disable-thp and the opt.thp to provide opt-out mechanisms for transparent huge page integration. (@jasone) - Update zone allocator integration to work with macOS 10.12. (@glandium) - Restructure *CFLAGS configuration, so that CFLAGS behaves typically, and EXTRA_CFLAGS provides a way to specify e.g. -Werror during building, but not during configuration. (@jasone, @ronawho) Bug fixes: - Fix DSS (sbrk(2)-based) allocation. This regression was first released in 4.3.0. (@jasone) - Handle race in per size class utilization computation. This functionality was first released in 4.0.0. (@interwq) - Fix lock order reversal during gdump. (@jasone) - Fix-refactor tcache synchronization. This regression was first released in 4.0.0. (@jasone) - Fix various JSON-formatted malloc_stats_print() bugs. This functionality was first released in 4.3.0. (@jasone) - Fix huge-aligned allocation. This regression was first released in 4.4.0. (@jasone) - When transparent huge page integration is enabled, detect what state pages start in according to the kernel's current operating mode, and only convert arena chunks to non-huge during purging if that is not their initial state. This functionality was first released in 4.4.0. (@jasone) - Fix lg_chunk clamping for the --enable-cache-oblivious --disable-fill case. This regression was first released in 4.0.0. (@jasone, @428desmo) - Properly detect sparc64 when building for Linux. (@glaubitz)
I ran a Try push off the rc-4.5.0 branch a few days ago without issue, so I'm not expecting any problems with the final release. But here's a new Try run just in case. https://treeherder.mozilla.org/#/jobs?repo=try&revision=d2c31d58ff45b60623535e8fc1175264f33639ac
Attachment #8842280 - Flags: review?(mh+mozilla)
(In reply to Ryan VanderMeulen [:RyanVM] from comment #1) > https://treeherder.mozilla.org/#/ > jobs?repo=try&revision=d2c31d58ff45b60623535e8fc1175264f33639ac And FWIW, the OSX logalloc-replay bustage is there for jemalloc4 builds in general, not a new issue with 4.5.0.
Can you file a bug for that one?
Heh, you already did. Bug 1343441
Attachment #8842280 - Flags: review?(mh+mozilla) → review+
Pushed by email@example.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/24bea8bde57d Update jemalloc 4 to version 4.5.0. r=glandium
Sorry had to back this out for build bustage like https://treeherder.mozilla.org/logviewer.html#?job_id=81017727&repo=mozilla-inbound&lineNumber=2784 https://hg.mozilla.org/integration/mozilla-inbound/rev/49e60602adda
Just needs a CLOBBER when relanding.
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/mozilla-inbound/rev/08fc65da8822 Update jemalloc 4 to version 4.5.0. r=glandium
You need to log in before you can comment on or make changes to this bug.