How to debug ROS2 Gazebo and VM Ubuntu Unresponsive? [closed]

asked 2021-07-08 22:59:32 -0500

RobotDreams gravatar image

updated 2021-07-09 09:16:23 -0500

Advice how to diagnose ROS2 Gazebo becoming unresponsive?

Symptom: After about three minutes with or without interaction Gazebo and the entire Ubuntu OS becomes unresponsive - cannot quit or shutdown. (I have to kill the virtual machine and restart it Ubuntu)

The system has been very stable when running ROS2 Nodes and Rviz2, but Gazebo is causing the Ubuntu OS to become unresponsive.

I am running
- ROS2 Foxy
- on Ubuntu 20.04.2 LTS 64-bit Desktop
- in an 8 GB Ram 3-cores available to VMware Fusion virtual machine
(4.7GB used when it becomes unresponsive)
- on a 32GB 3.2GHz 6-Core Intel Core i7 2018 MacMini
- with Intel UHD Graphics 630, and Radeon RX580 w/8GB Video RAM
- running macOS Big Sur 11.0.1

edit retag flag offensive reopen merge delete

Closed for the following reason question is not relevant or outdated by RobotDreams
close date 2022-11-19 22:41:21.639936

Comments

2

Would this not be something to ask over at answers.gazebosim.org? Gazebo is not an integral part of ROS, it's a stand-alone application which happens to have plugins which allow it to communicate with a ROS application.

gvdhoorn gravatar image gvdhoorn  ( 2021-07-09 03:21:56 -0500 )edit

@gvdhoorn pointed you in a good direction. I am sure that in Gazebo answers you will find more help than here. However, I would say that your problem seems to come from your Virtual environment. Gazebo and Virtualuzed Desktops do no get along very well when 3D graphics acceleration is turned on in the Virtual Machine settings.

Weasfas gravatar image Weasfas  ( 2021-07-09 05:25:18 -0500 )edit

Would this not be something to ask over at answers.gazebosim.org? Gazebo is not an integral part of ROS, it's a stand-alone application which happens to have plugins which allow it to communicate with a ROS application.

Thanks, did not know that.

RobotDreams gravatar image RobotDreams  ( 2021-07-09 06:36:34 -0500 )edit
add a comment