This error is not a standard ROS output. Instead, it typically surfaces when a custom rqt plugin or a node named "Odin" (a common internal codename for autonomy stacks, custom executors, or specific robotic platforms) fails to close its ROS GUI components gracefully. The rqtclose signal indicates that the GUI was either forcibly terminated, lost a connection to the ROS master, or encountered a deadlock during shutdown.
ODIN nodes often output high-frequency data (e.g., 100 Hz IMU, 30 Hz camera). If you use rqt_plot to visualize multiple topics without throttling, rqt may consume so much memory that the OS kills either rqt or the ODIN node (via OOM killer). This can appear as an unexplained "close." odin rqtclose