Closed Bug 1808429 Opened 1 year ago Closed 1 year ago

Make it easier to configure poisoning in jemalloc at runtime

Categories

(Core :: Memory Allocator, task, P1)

task

Tracking

()

RESOLVED FIXED
111 Branch
Tracking Status
firefox111 --- fixed

People

(Reporter: pbone, Assigned: pbone)

References

(Blocks 1 open bug)

Details

(Whiteboard: [sp3])

Attachments

(3 files)

I have some patches that make it possible to turn poisoning in jemalloc off and on at runtime.

This comment refers to parameters that don't exist. I assume it's
obsolete.

Poisoning was hardcoded, but to compare different allocators I wanted to
disable it. This patch lets us control poisoning with the MALLOC_OPTIONS
environment variable.

Depends on D165918

Some of the runtime options are compiled-in constants when MOZ_DEBUG is not
defined. But it can be useful to enable these configuration options without
enabling the rest of MOZ_DEBUG (eg assertions). This patch adds a new
preprocessor macro to enable runtime configuration.

Depends on D165919

Attachment #9310591 - Attachment description: Bug 1808429 - Remove obsolete comment r=glandium → Bug 1808429 - Fix non-existant parameters in code comment r=glandium
Pushed by pbone@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/db41ee75c736
Fix non-existant parameters in code comment r=glandium
https://hg.mozilla.org/integration/autoland/rev/c2eabcd996d7
Add the ability to enable and disable poisoning r=glandium
https://hg.mozilla.org/integration/autoland/rev/704ccaff06dd
Disconnect runtime configuration from MOZ_DEBUG r=glandium
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 111 Branch
Whiteboard: [sp3]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: