[R] Fix memory safety issues#11847
Merged
Merged
Conversation
Member
|
Thank you for the quick fix! |
Member
Sounds good! Thank you for carrying it to the finish line. |
trivialfis
pushed a commit
to trivialfis/xgboost
that referenced
this pull request
Jan 3, 2026
trivialfis
pushed a commit
to trivialfis/xgboost
that referenced
this pull request
Jan 3, 2026
trivialfis
added a commit
that referenced
this pull request
Jan 4, 2026
Co-authored-by: david-cortes <[email protected]>
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
2 participants
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.
Fixes a few issues detected by rchk.
@trivialfis You'll likely be asked to resubmit a fixed version of xgboost to CRAN after a few days. This PR will need to be backported if there isn't any 3.2 release by then. There might be more required changes from other checks, so let's wait for their email before resubmitting.