A ROS2 navigation stack running perfectly for two days, then: segfault.
This happened on a Jetson Xavier NX running a multi-sensor fusion pipeline. The node would start clean, pass all integration tests, run flawlessly through the first 24 hours of continuous operation. Then somewhere around the 47-48 hour mark, it would die with a cryptic std::bad_alloc or just vanish from ros2 node list.
The logs were useless. No warnings. No gradual performance degradation. Just sudden death.
Turns out the culprit wasn't ROS2 itself — it was the intersection of three things: DDS middleware default settings, unbound message queues, and Jetson's 8GB RAM constraint. The fix took 15 minutes once I knew where to look. The investigation took three days.
What Actually Kills Long-Running Nodes
Continue reading the full article on TildAlice
Top comments (0)