Assign nullptr to spin_thread_ after deletion #30
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.
In class BaseCostmapToPolygons, spin_thread_ pointer variable is used to check if thread should be stopped and join.
After deletion in stopWorker ptr was never set to nullptr, so second call to stopWorker blocks forever.
This bug prevent TEB planner from being used in lifecycle node, because BaseCostmapToPolygons cannot be stopped then destructed.
Solution is to set spin_thread_ to null after deletion. In future, it will be more reliable to use smart pointers instead of raw.