Update - #878
Merged
Merged
Conversation
Development
setcopyv() wrote element pointers directly into STRSXP/VECSXP backing arrays, skipping R's generational write barrier. On an old-generation target this can leave an unrecorded reference to a younger CHARSXP/list element, which a subsequent young-generation GC may free while still referenced, causing memory corruption, cryptic CHAR()/SET_STRING_ELT() errors, or segfaults. Use SET_STRING_ELT()/SET_VECTOR_ELT() for the boxed-type write loops so the reference is properly recorded, while leaving the numeric/raw branches unchanged. Also drops the omp simd pragma from the boxed write paths, since the barriered setters are function calls and are not safely vectorizable. Co-authored-by: Sebastian Krantz <48053842+SebKrantz@users.noreply.github.com>
Fix: write barrier bypass in setv()/copyv() for STRSXP/VECSXP targets
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.
No description provided.