Use ceiling for history frequency calculation#81
Merged
Conversation
Change integer division to use ceiling function for history frequency. This should resolve a potential out of bounds array access when writing history where steps does not cleanly divide logging frequency.
Member
Author
|
This is based on the CRAN valgrind log Which points to this line: Line 298 in 93ecf36 I'm personally surprised that this achieves an access violation, as opposed to throwing an out of bounds exception as I didn't think RCpp vectors were C style arrays. |
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.
Change integer division to use ceiling function for history frequency. This should resolve a potential out of bounds array access when writing history where steps does not cleanly divide logging frequency.
I think this will resolve the memory-leak reported by CRAN, via some pen & paper maths, however I wasn't able to reproduce the valgrind error locally so I'm unable to confirm that.