-
Notifications
You must be signed in to change notification settings - Fork 29
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
process exits abnormally with range check exception #23
Comments
Thanks for noticing, this seems to be a bug which transferred form the ROS1 version to the ROS2 version. |
Still in latest version:
I will try to reproduce this in a |
Hi, |
The ROS2 node itself doesn't crash, and continues to publish diagnostic_msgs, but stops publishing scan data, which suggests that one of the threads spawned internally exits. It seems to happen usually after over 24 hours. I will setup gdb and try to get a backtrace. |
@YannickdeHoop fyi |
Here's the stacktrace
locals at frame 10 (createLaserScanMsg):
locals at frame 11(receiveUDPPaket):
locals at frame 13(processUDPPacket):
|
Thanks for the stacktrace! This will hopefully help in fixing the issue. |
Please check if c8e4b0d resovled the issue |
The fix is included in the newest release 1.0.4, which will be rolled out with the next sync of each distro. Therefore, this should be fixed, if not please reopen or make a new issue |
after four hours of running happily, the sick_safetyscanners2_node process exited with
vector::_M_range_check: __n (which is 18446744073709551615) >= this->size() (which is 0)
probably not easy to reproduce, its the first time I've seen it. But worth logging.
Interesting the size of the vector is 0, and the index is probably -1. Perhaps that offers some clues.
The only code i've seen that looks like that is here
sick_safetyscanners2/src/utils/MessageCreator.cpp
Line 179 in 6824138
But it would never have entered the loop if the size was 0
The text was updated successfully, but these errors were encountered: