feat: expose APIs to bind custom memory allocators #3896
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The example was causing unit test failures because it was being included in workspace tests. Moved it to be a standalone workspace member.
Added a CI job to verify both basic and jemalloc custom allocator examples work correctly.
Added a CI job to verify both basic and jemalloc custom allocator examples work correctly.
The doctest example uses jemallocator which is not available in the test environment. Changed from no_run to ignore to prevent compilation errors.
|
I'm closing this because it's possible to use |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related to #3895.
I would like to use jemalloc to diagnose memory leaks and track heap usage.