Split out --enable-tracy-memory-tracking, disabled by default #4512
+14
−4
Conversation
This file contains 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
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.
This splits out the memory-tracking machinery of tracy and disables it by default unless the user configures with
--enable-tracy-memory-tracking. In practice we seem to use this much less often than normal tracy, and it has a much higher overhead -- enough to become nonresponsive under load -- so turning it off makes tracy more usable more of the time.It's also mutually exclusive with asan, and we used to just silently disable the memory-tracking part of tracy when asan was on, but I changed it to notice and complain when you use asan with this new flag specifically. Seems a better (less head-scratching) experience than just silently not-getting the instrumentation.