micro-ROS / micro-ROS/micro-ROS-Agent

'eprosima::fastcdr::exception::NotEnoughMemoryException' what(): Not enough memory in the buffer stream error

Open
#266 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
C++
Stars
201
Forks
111
Avg merge
1d 6h
Merged PRs (30d)
10

Description

Hello?

Ubuntu version : 22.04
ROS2 version : Humble

When running micro-ros-agent, the following error occurs:

terminate called after throwing an instance of 'eprosima::fastcdr::exception::NotEnoughMemoryException' what(): Not enough memory in the buffer stream

Let me explain some situations when that error occurs.

1. When running micro-ROS-agent on a Linux PC with Ubuntu22.04, ROS2 Humble installed, this device and another device are connected to the same network as a Linux PC with Ubuntu24.04, ROS Jazzy installed.

2. When running micro-ROS-agent on a Linux PC with Ubuntu22.04, ROS2 Humble installed, when connecting to the same network as this device and another device with a Linux PC with Ubuntu24.04, ROS Jazzy installed and running ROS2 Node via SSH.

3. When running micro-ROS-agent on a Linux PC with Ubuntu22.04, ROS2 Humble installed, when connecting to the same network as this device and another device with a Linux PC with Ubuntu24.04, ROS Jazzy installed, and entering ROS2 commands such as the ros2 topic list command and the ros2 topic echo /topic1 command via SSH.

This situation has occurred quite frequently, and my question is as follows:

1. Do you know how to fix the following error?

terminate called after throwing an instance of 'eprosima::fastcdr::exception::NotEnoughMemoryException' what(): Not enough memory in the buffer stream

2. Can that error occur simply because devices with different ROS2 versions (Humble, Jazzy) are connected to the same network?

3. When devices with different ROS2 versions (Humble, Jazzy) are connected to the same network, can an error occur simply by entering the command to connect via SSH?

4. When devices with different ROS2 versions (Humble, Jazzy) are connected to the same network, can the error occur when entering ROS2 commands or running ROS2 nodes?

If you know any of the questions I'm asking above, please help me.

Thank you.

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the micro-ROS-agent failure in the Ubuntu 22.04/ROS 2 Humble and Ubuntu 24.04/ROS 2 Jazzy network scenarios described, including the SSH and ROS 2 command cases. Determine whether mixed ROS 2 versions trigger the Fast CDR exception, then document the root cause, compatibility requirements, and a verified resolution.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
distributed-systems, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.