rviz2 libc++abi.dylib: terminating with uncaught exception
I'm trying to run the turtlebot_simulation using the command
ros2 launch turtlebot3_fake_node turtlebot3_fake_node.launch.py
This causes rviz2 to crash. I'm running on MacOs (Mohave) here's the trace:
[INFO] [launch]: All log files can be found below /Users/ros/.ros/log/2020-12-01-22-32-32-300026-MartinsMBP9114.domain-93568
[INFO] [launch]: Default logging verbosity is set to INFO
/Users/ros/turtlebot3_ws/install/turtlebot3_fake_node/share/turtlebot3_fake_node/launch/turtlebot3_fake_node.launch.py:63: UserWarning: The parameter 'node_executable' is deprecated, use 'executable' instead
Node(
/Users/ros/turtlebot3_ws/install/turtlebot3_fake_node/share/turtlebot3_fake_node/launch/turtlebot3_fake_node.launch.py:69: UserWarning: The parameter 'node_executable' is deprecated, use 'executable' instead
Node(
/Users/ros/turtlebot3_ws/install/turtlebot3_fake_node/share/turtlebot3_fake_node/launch/turtlebot3_fake_node.launch.py:69: UserWarning: The parameter 'node_name' is deprecated, use 'name' instead
Node(
[INFO] [launch.user]: Execute Turtlebot3 Fake Node!!
/Users/ros/turtlebot3_ws/install/turtlebot3_fake_node/share/turtlebot3_fake_node/launch/rviz2.launch.py:31: UserWarning: The parameter 'node_executable' is deprecated, use 'executable' instead
Node(
/Users/ros/turtlebot3_ws/install/turtlebot3_fake_node/share/turtlebot3_fake_node/launch/rviz2.launch.py:31: UserWarning: The parameter 'node_name' is deprecated, use 'name' instead
Node(
[INFO] [rviz2-1]: process started with pid [93572]
[INFO] [turtlebot3_fake_node-2]: process started with pid [93573]
[INFO] [robot_state_publisher-3]: process started with pid [93574]
[robot_state_publisher-3] [WARN] [1606890752.539500531] [robot_state_publisher]: No robot_description parameter, but command-line argument available. Assuming argument is name of URDF file. This backwards compatibility fallback will be removed in the future.
[turtlebot3_fake_node-2] [INFO] [1606890752.541841254] [turtlebot3_fake_node]: Turtlebot3 fake node has been initialised
[robot_state_publisher-3] Parsing robot urdf xml string.
[robot_state_publisher-3] Link base_link had 5 children
[robot_state_publisher-3] Link caster_back_link had 0 children
[robot_state_publisher-3] Link imu_link had 0 children
[robot_state_publisher-3] Link base_scan had 0 children
[robot_state_publisher-3] Link wheel_left_link had 0 children
[robot_state_publisher-3] Link wheel_right_link had 0 children
[robot_state_publisher-3] [INFO] [1606890752.550636401] [robot_state_publisher]: got segment base_footprint
[robot_state_publisher-3] [INFO] [1606890752.550679245] [robot_state_publisher]: got segment base_link
[robot_state_publisher-3] [INFO] [1606890752.550697443] [robot_state_publisher]: got segment base_scan
[robot_state_publisher-3] [INFO] [1606890752.550713655] [robot_state_publisher]: got segment caster_back_link
[robot_state_publisher-3] [INFO] [1606890752.550729976] [robot_state_publisher]: got segment imu_link
[robot_state_publisher-3] [INFO] [1606890752.550746353] [robot_state_publisher]: got segment wheel_left_link
[robot_state_publisher-3] [INFO] [1606890752.550762400] [robot_state_publisher]: got segment wheel_right_link
[rviz2-1] [INFO] [1606890753.442791934] [rviz2]: Stereo is NOT SUPPORTED
[rviz2-1] [INFO] [1606890753.443083417] [rviz2]: OpenGl version: 2.1 (GLSL 1.2)
[rviz2-1] [INFO] [1606890753.567011273] [rviz2]: Stereo is NOT SUPPORTED
[rviz2-1] libc++abi.dylib: terminating with uncaught exception of type std::__1::system_error: mutex lock failed: Invalid argument
[ERROR] [rviz2-1]: process has died [pid 93572, exit code -6, cmd '/Users/ros/ros2_foxy/ros2-osx/lib/rviz2/rviz2 -d /Users/ros/turtlebot3_ws/install/turtlebot3_fake_node/share/turtlebot3_fake_node/rviz/model.rviz --ros-args -r __node:=rviz2 -r __node:=rviz2'].
Can anyone help me with this issue?
We would need more context, can you try to modify the launch file so that it does not run rviz, and instead run rviz manually after running the launch file? It would also be useful to have a traceback from lldb when rviz crashes, so we know where it is coming from.