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
I'm encountering a segmentation fault when running the schedule_visualizer_node. The node crashes with exit code -11. This issue occurs sometimes in the Middel of process and prevents the schedule visualization from working. [ERROR] [schedule_visualizer_node-4]: process has died [pid 3072018, exit code -11, cmd '/home/nanofleet/nrmf_ws/install/rmf_visualization_schedule/lib/rmf_visualization_schedule/schedule_visualizer_node --ros-args --params-file ... ']
Steps to reproduce the bug
.
Expected behavior
No response
Actual behavior
No response
Additional information or screenshots
No response
The text was updated successfully, but these errors were encountered:
Kindly provide discrete steps that we can follow to reproduce the behavior. If you could provide a gdb backtrace, that will be very helpful as well. Ideally there is a demo package we can run to see the same behavior.
Before proceeding, is there an existing issue or discussion for this?
OS and version
Ubuntu 22.04.4 LTS
Open-RMF installation type
Source build
Other Open-RMF installation methods
No response
Open-RMF version or commit hash
main
ROS distribution
Humble
ROS installation type
Binaries
Other ROS installation methods
No response
Package or library, if applicable
No response
Description of the bug
I'm encountering a segmentation fault when running the schedule_visualizer_node. The node crashes with exit code -11. This issue occurs sometimes in the Middel of process and prevents the schedule visualization from working.
[ERROR] [schedule_visualizer_node-4]: process has died [pid 3072018, exit code -11, cmd '/home/nanofleet/nrmf_ws/install/rmf_visualization_schedule/lib/rmf_visualization_schedule/schedule_visualizer_node --ros-args --params-file ... ']
Steps to reproduce the bug
.
Expected behavior
No response
Actual behavior
No response
Additional information or screenshots
No response
The text was updated successfully, but these errors were encountered: