Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

DNM: Try out jemalloc leak profiling #31049

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

DNM: Try out jemalloc leak profiling #31049

wants to merge 1 commit into from
+9 −1

Conversation

def-
Copy link
Contributor

@def- def- commented Jan 15, 2025 •
edited
Loading

Motivation is to find memory leaks in CI, want to evaluate if this works at all first

See https://github.com/jemalloc/jemalloc/wiki/Use-Case%3A-Leak-Checking

Checklist

  • This PR has adequate test coverage / QA involvement has been duly considered. (trigger-ci for additional test/nightly runs)
  • This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
  • If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
  • If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).
  • If this PR includes major user-facing behavior changes, I have pinged the relevant PM to schedule a changelog post.

@def-
DNM: Try out jemalloc leak profiling
90e4720 
Motiviation is to find memory leaks in CI, want to evaluate if this
works at all first

See https://github.com/jemalloc/jemalloc/wiki/Use-Case%3A-Leak-Checking
@def- def- force-pushed the pr-leak-profiling branch from c3e0805 to 90e4720 Compare January 15, 2025 17:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@teskje teskje Awaiting requested review from teskje teskje will be requested when the pull request is marked ready for review teskje is a code owner

At least 1 approving review is required to merge this pull request.

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@def-