Fix dereferencing a dangling pointer in WorldNode #1311
Merged
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.
InclearUnusedNodes()
, if an unused node doesn't have any holders that have the ownership, it becomes dangling pointers sinceWorldNode
holds nodes as raw pointers.In
clearUnusedNodes()
, an unused node is possible to hold a dangling pointer toShapeFrame
. This can happen becauseShapeFrameNode
doesn't have the ownership ofShapeFrame
. This leads to dereferencing a dangling pointer in the logic of checking whether the node is shadowed or not.This PR changes the behavior of the node deletion logic to remove the access to the internal
ShapeFrame
pointer. Instead, it now unconditionally removes the node from both of shadowed group and unshadowed group. I believe this is safe because OSG will ignore the attempt of removing a non-existing node in the group.Before creating a pull request
clang-format
Before merging a pull request
CHANGELOG.md