micro-ROS / micro-ROS/micro-ROS-Agent
'eprosima::fastcdr::exception::NotEnoughMemoryException' what(): Not enough memory in the buffer stream error
Personne n'a encore pris cette issue.
- Langage dominant
- C++
- Étoiles
- 201
- Forks
- 111
- Merge moyen
- 1 j 6 h
- PR mergées (30 j)
- 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.
Guide de contribution
Ouvrir le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Piste de recherche
Commencez par reproduire l’échec de micro-ROS-agent dans les scénarios réseau décrits Ubuntu 22.04/ROS 2 Humble et Ubuntu 24.04/ROS 2 Jazzy, y compris les cas de commandes SSH et ROS 2. Déterminez si des versions mixtes de ROS 2 déclenchent l’exception Fast CDR, puis documentez la cause racine, les exigences de compatibilité et une résolution vérifiée.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- cpp
- Domaine
- distributed-systems, networking
- Type d'issue
- Bug
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- Calme
- Clarté
- À clarifier
- Accessibilité débutants
- 42/100