You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Nodes on the same device use shared memory to transfer data normally
Current behavior
At first the nodes could communicate with each other normally, but after a while the consumer could not receive the data, and the shared memory file under /dev/shm disappeared
Steps to reproduce
There are about 30 nodes on a single device, and they will communicate with each other and run for a period of time. But it's not a must-appear, I didn't have this issue on x86, but I had it on an ARM board
Fast DDS version/commit
2.6.8,2.6.9
Platform/Architecture
Other. Please specify in Additional context section.
Transport layer
Shared Memory Transport (SHM)
Additional context
linux version: ubuntu22.04
platform: arm64
ros2: humble
XML configuration file
default configuration
Relevant log output
No response
Network traffic capture
No response
The text was updated successfully, but these errors were encountered:
Is there an already existing issue for this?
Expected behavior
Nodes on the same device use shared memory to transfer data normally
Current behavior
At first the nodes could communicate with each other normally, but after a while the consumer could not receive the data, and the shared memory file under /dev/shm disappeared
Steps to reproduce
There are about 30 nodes on a single device, and they will communicate with each other and run for a period of time. But it's not a must-appear, I didn't have this issue on x86, but I had it on an ARM board
Fast DDS version/commit
2.6.8,2.6.9
Platform/Architecture
Other. Please specify in Additional context section.
Transport layer
Shared Memory Transport (SHM)
Additional context
linux version: ubuntu22.04
platform: arm64
ros2: humble
XML configuration file
Relevant log output
No response
Network traffic capture
No response
The text was updated successfully, but these errors were encountered: