micro-ROS / micro-ROS/micro-ROS-Agent
'eprosima::fastcdr::exception::NotEnoughMemoryException' what(): Not enough memory in the buffer stream error
Nadie ha tomado este issue todavía.
- Lenguaje dominante
- C++
- Estrellas
- 201
- Forks
- 111
- Merge medio
- 1 d 6 h
- PR fusionados (30 d)
- 10
Descripción
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.
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Línea de trabajo
Comience reproduciendo el fallo de micro-ROS-agent en los escenarios de red descritos de Ubuntu 22.04/ROS 2 Humble y Ubuntu 24.04/ROS 2 Jazzy, incluidos los casos de comandos SSH y ROS 2. Determine si las versiones mixtas de ROS 2 desencadenan la excepción de Fast CDR y, a continuación, documente la causa raíz, los requisitos de compatibilidad y una resolución verificada.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- cpp
- Área
- distributed-systems, networking
- Tipo de issue
- Error
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Tranquilo
- Claridad
- Necesita aclaración
- Aptitud para principiantes
- 42/100