micro-ROS / micro-ROS/micro-ROS-Agent
'eprosima::fastcdr::exception::NotEnoughMemoryException' what(): Not enough memory in the buffer stream error
Ninguém assumiu esta issue ainda.
- Linguagem predominante
- C++
- Estrelas
- 201
- Forks
- 111
- Merge médio
- 1d 6h
- PRs com merge (30d)
- 10
Descrição
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.
-
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.
-
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.
-
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:
- 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
-
Can that error occur simply because devices with different ROS2 versions (Humble, Jazzy) are connected to the same network?
-
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?
-
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.
Guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Direção de pesquisa
Comece reproduzindo a falha do micro-ROS-agent nos cenários de rede descritos do Ubuntu 22.04/ROS 2 Humble e Ubuntu 24.04/ROS 2 Jazzy, incluindo os casos de comandos SSH e ROS 2. Determine se versões diferentes do ROS 2 acionam a exceção do Fast CDR e, em seguida, documente a causa raiz, os requisitos de compatibilidade e uma resolução verificada.
Escrita pelo modelo de indexação a partir do texto da issue.
Avaliação
- Stack de tecnologia
- cpp
- Domínio
- distributed-systems, networking
- Tipo de issue
- Bug
- Dificuldade
- 4/5
- Tempo estimado
- 3-5 dias
- Status de atividade
- Pouca atividade
- Clareza
- Precisa de esclarecimento
- Facilidade para iniciantes
- 42/100