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.
Prior to Julia 1.9
--track-allocation
was one of the only ways to track where allocations where coming from in Julia.The way it functions is to change the emitted LLVM IR to insert code that tracks allocations occuring.
This often leads to false-positives since these statements interfere with optimization (in particular escape analysis)
and @simonbyrne and I once spend a particular fun couple of days hunting down ghosts.
Since it changes the emitted code it also does not particular play well with package images.
I believe there is no remaining use-case for
--track-allocation
that would not be better served by using the allocation profiler,and I am proposing to remove of the
--track-allocation
feature in 1.10.Are there users of
--track-allocation
that would object? Are there use-cases where you have fund it particular useful that are not covered by the allocation profiler?