Fix one joint trajectory controller case of std::runtime_error Duration is out of dual 32-bit range #577
Conversation
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
Duration is out of dual 32-bit range that came from initializing a ros::Duration with an uninitialized double
This was referenced Oct 28, 2021
|
I am looking forward to seeing this change merged. |
|
I am also experiencing this problem on my Ubuntu 20.04 installation running a 5.13.0-35-generic kernel. The problem does not happen every time but comes on a random basis. I installed the Debian package's joint-trajectory controller (version 0.19.0-1focal.20220221.105035 amd64). |
bmagyar
approved these changes
Mar 17, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
I was able to pin down the exception to a ros::Duration with an uninitialized double- possibly random bits will sometimes produce a usable value, but on my system the exception was very frequent.
Probably this has been lurking here since
time_from_startwas introduced 7fac696There are some issues and answers posts with the same exception that probably are a similar cause (in one there's an uninitialized
Rateobject which it sounded like the user corrected in their own code, but really Rate should always initialize to 0), but predate this particular one.