Fix crash when setting covariance using null quaternion #1180
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.
This is an alternative fix for #1137. The current fix in place is from #1139 which prevented the crash by rejecting the invalid quaternions.
The root cause of the crash was that, although the null quaternion is set to identity in
FrameManager::transform()
at this line, it was still using the null quaternion for the covariance display.This will allow us to not reject null quaternions, which is important given the prevalence of invalid quaternions as uncovered by #1167