Optional memory profiling - #41
Merged
Merged
Conversation
kmokstad
force-pushed
the
mempoll
branch
2 times, most recently
from
January 24, 2026 10:27
776351f to
7498817
Compare
readFileHeader() and buildAndResolveHierarchy().
Add optional doMemPoll argument to the methods doResultFilesUpdate() and addFiles(), which is passed on to doResultFileUpdate(), updateExtractorHeader() and FFrResultContainer::updateStatus().
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 adds a bool argument
memPoll(ordoMemPoll) to some methods that are equipped with memory profiling (withFT_USE_PROFILERis defined compile time). This is used by the GUI, which have a private-memPollcommand-line option to activate memory profiling at run-time. The value of this option can then be passed down to this submodule such that the behavior here is aligned with the main application.