-
Notifications
You must be signed in to change notification settings - Fork 773
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
std::out_of_range with map::at exception with gtsam 4.1.1 (rtabmap) #1092
Comments
I have run into this problem as well, and have developed a minimal example that demonstrates it (see below). I originally came across it when working with KimeraRPGO, but have also found it in a custom algorithm. It would appear that the common behavior of However, I have also found that the bug is reproducible even when the incremental adding of factors is omitted, and rather any repeated call to In my testing I have noticed the following about the bug:
Technical Details:
Incremental Factors Example
Bare-Bones Example
|
Update: I have confirmed that running on v4.0.3 (built from source) the above examples do not appear to error out. |
Hi @DanMcGann, are you using TBB? |
Yes, |
It would be great if you can try
|
So a brief review:
So I am thinking about a race condition in the graph traversal task. |
I'll take a closer look at this either this week or next week. Having a race condition is not really acceptable. |
Confirmed: Tested this morning with these commits reverted and I cannot seem to re-recreate the bug. |
@acxz Do you have time to take a look? BTW, I suspect it could be a missing |
Sorry about the delay, not yet sadly. Yeah thats a good hunch you have. |
I have half a roadmap for fixing this issue. This is due to the old I still have to debug where the problem exact is. |
Hi, I am using rtabmp with gtsam 4.1.1. It occasionally occurs terminate called after throwing an instance of 'std::out_of_range'
what(): map::at.
The details are similar to
introlab/rtabmap#823
I hope it could be fixed soon. Maybe you could work it out together @matlabbe.
I give a reprint here.
The text was updated successfully, but these errors were encountered: