-
Notifications
You must be signed in to change notification settings - Fork 61
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
terminate called after throwing an instance of 'std::bad_alloc' #214
Comments
Hello @Ryanf55, this is a well-known problem and IMO not really a micro-ROS issue. The key is that the ROS 2
Specifically, if your Humble installation receives an Iron In summary, this is a ROS 2 distro incompatibility issue and shall be solved if you ensure that your Humble environment does not have any interaction with an Iron environment (local or remote). |
HI Pablo, thanks for the info. Just FYI, I do not have Iron installed, and there are no other ROS 2 developers on my home network, so I don't think that's the issue. Everything is on humble. Ardupilot targets ros2 humble only. |
You have the very same error that we found some weeks ago. How are you building the micro-ROS Agent? Because of this line |
We are building the micro-ROS with colcon, with the Fast-dds is installed with the humble binaries. |
Can you provide a Dockerfile with a replicator without the Ardupilot part? |
I can try. The MicroXRCE DDS Agent is heavily tied to ArduPilot right now; it may be hard to build a standalone example to reproduce. Would it be acceptable to provide a dockerfile with ArduPilot already built and running? Then you can just run it against MicroROS on your host OS built with debug and run under GDB? |
That would be acceptable as far as everything runs inside a Docker. |
Thanks. Can you assign this ticket to me. I can get you the info a few days. |
Describe the bug
When running the MicroROS agent, it periodically crashes with
std::bad_alloc
.To Reproduce
Steps to reproduce the behavior:
Expected behaviour
The agent runs reliably without an allocation error.
System information (please complete the following information):
3.0.5
Additional context
Here's the debug logs at verbosity 6 while running under gdb:
The text was updated successfully, but these errors were encountered: