Flush buffers before reading back in to construct all seen addresses #206
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.
When disabling profiling, the log of samples written is read back in by
LogReaderDumpNative
to construct a deduplicated set of all code addresses that were recorded during sampling. This set is then passed to_vmprof.write_all_code_objects
to write out the address and file/symbol info.However if the last call to
commit_buffer
is a short write (for example because it was interrupted by a signal), then the LogReader may not be able to parse the tail of the file because we may still have pending un-flushed buffers (see:_write_single_ready_buffer
).This change adds a function to ensure all pending buffers are flushed to disk before attempting to reread them with the LogReader.