fix(profiling): guard against invalid access on exit#17180
Draft
KowalskiThomas wants to merge 1 commit intomainfrom
Draft
fix(profiling): guard against invalid access on exit#17180KowalskiThomas wants to merge 1 commit intomainfrom
KowalskiThomas wants to merge 1 commit intomainfrom
Conversation
Contributor
|
I can only run on private repositories. |
Codeowners resolved as |
bbd8d23 to
ebd369e
Compare
This comment has been minimized.
This comment has been minimized.
Co-authored-by: KowalskiThomas <14239160+KowalskiThomas@users.noreply.github.com>
ebd369e to
8dc485a
Compare
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
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.
Description
This PR addresses a crash that can occur at process exit if the Sampling thread failed to stop within the allowed time. When this happens, we would previously still free the
Samplerobject (through implicit destruction of thestd::unique_ptr) and the Sampling Thread could then try to read data from e.g. theStringTablewhich was being or had been deleted.Note I don't have any proof that the crash is caused by this specific code path, but it does make sense to me because in that case, we would definitely crash. So regardless, it's probably worth "fixing" (even though we're working around and not really properly fixing here -- I just don't see another way).