New release?

[vtsao-openai]

Can we get a new release for this library? I want to get this into the BCR (https://github.com/bazelbuild/bazel-central-registry/issues/3757) and would be great if we could use a new version.

[interwq]

Hi @vtsao-openai , the next release is likely to happen in H2. We have a few bigger changes in progress, mainly around the huge page topics. We are also trying to make huge page related features enabled by default.

[mathomp4]

Ahh. I was about to ask about this. I work with a model that is looking to use jemalloc and I noticed the last release was 3 years ago, but the last commit was last week.

Are there any "caveats" with jemalloc 5.3.0? I'd be using it on AMD Epyc nodes which were fairly new back in 2022, and I don't know if there are issues and instead I should build jemalloc from dev say instead of 5.3.0 in my testing?

[paravoid]

With my Debian maintainer hat on... unless a release happens in the next week or so (which from what I gather it's not going to happen) we are going to have release our next Debian release, trixie, with jemalloc 5.3.0. This is the version that we shipped with Debian bookworm as well. Not the worst outcome in the world (it's well-tested after all!), but it's kind of a pity to miss 2+ years of upstream development. It'd be great if you could release newer versions more often in the future. Something like 6-12 months would be ideal for downstreams, I think!

[vtsao-openai]

Not really related to a new release, but looks like somebody else Bazel-fied the latest release version into the BCR: https://github.com/bazelbuild/bazel-central-registry/pull/3896

But would still be good to get a new release.

[orlp]

@interwq Would it be possible to take a look at https://github.com/jemalloc/jemalloc/issues/2688#issuecomment-2277830712 before the next release? muzzy_decay_ms > 0 is completely ignored and acts the same as muzzy_decay_ms = 0 (instantly unmapping the dirty page). This is causing us to have to choose between an inflated RSS due to only emitting MADV_FREE (muzzy_decay_ms = -1) or bad performance.

[dasergatskov]

The current release on MacOS/Homebre causes octave to crash (to be more specific the octave-svgconvert uility would crash) with:

(lldb) run
Process 34787 launched: '/Users/dmitri/src/octave/out_gopt/src/octave-svgconvert' (arm64)
Process 34787 stopped
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x6478)
    frame #0: 0x000000010074ec24 libjemalloc.2.dylib`je_free_default + 156
libjemalloc.2.dylib`je_free_default:
->  0x10074ec24 <+156>: ldr    x8, [x0]
    0x10074ec28 <+160>: lsr    x3, x8, #48
    0x10074ec2c <+164>: adrp   x9, 360
    0x10074ec30 <+168>: add    x9, x9, #0x3c0 ; je_sz_index2size_tab
Target 0: (octave-svgconvert) stopped.
(lldb)

No problem with current git

% git rev-parse HEAD
3688dfb5c3b7d94a12e18b753c0fc9c405b77b1f

So to have an earlier release would be helpful.