Gazebo | Ignition | Community
Ask Your Question

On startup of gazebo I get intermittent error

asked 2013-12-15 10:29:27 -0500

rnunziata gravatar image

updated 2013-12-15 10:31:05 -0500

On startup of gazebo I get intermittent error. Are there any ideas on what causes this?

viki@viki:~$ roslaunch rrbot_gazebo rrbot.launch 
... logging to /home/viki/.ros/log/9899e8d6-65a5-11e3-8f5b-28cfe95d78b1/roslaunch-viki-15818.log
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.

started roslaunch server http://viki:36669/


 * /rosdistro
 * /rosversion
 * /use_sim_time

    gazebo (gazebo_ros/gzserver)
    gazebo_gui (gazebo_ros/gzclient)

auto-starting new master
process[master]: started with pid [15832]

setting /run_id to 9899e8d6-65a5-11e3-8f5b-28cfe95d78b1
process[rosout-1]: started with pid [15845]
started core service [/rosout]
process[gazebo-2]: started with pid [15859]
process[gazebo_gui-3]: started with pid [15864]
Gazebo multi-robot simulator, version 1.9.1
Copyright (C) 2013 Open Source Robotics Foundation.
Released under the Apache 2 License.

Gazebo multi-robot simulator, version 1.9.1
Copyright (C) 2013 Open Source Robotics Foundation.
Released under the Apache 2 License.

Msg Waiting for master.[ INFO] [1387124766.405464458]: Finished loading Gazebo ROS API Plugin.
[ INFO] [1387124766.407054987]: waitForService: Service [/gazebo/set_physics_properties] has not been advertised, waiting...
Msg Waiting for master
Msg Connected to gazebo master @
Msg Publicized address:

Msg Connected to gazebo master @
Msg Publicized address:
X Error of failed request:  BadDrawable (invalid Pixmap or Window parameter)
  Major opcode of failed request:  152 (DRI2)
  Minor opcode of failed request:  3 (DRI2CreateDrawable)
  Resource id in failed request:  0x4600002
  Serial number of failed request:  29
  Current serial number in output stream:  31
gzclient: /usr/include/boost/smart_ptr/shared_ptr.hpp:424: T* boost::shared_ptr<T>::operator->() const [with T = gazebo::transport::Connection]: Assertion `px != 0' failed.
Aborted (core dumped)
[gazebo_gui-3] process has died [pid 15864, exit code 134, cmd /opt/ros/hydro/lib/gazebo_ros/gzclient __name:=gazebo_gui __log:=/home/viki/.ros/log/9899e8d6-65a5-11e3-8f5b-28cfe95d78b1/gazebo_gui-3.log].
log file: /home/viki/.ros/log/9899e8d6-65a5-11e3-8f5b-28cfe95d78b1/gazebo_gui-3*.log
[ INFO] [1387124767.977077948]: Loading gazebo_ros_control plugin
[ INFO] [1387124767.977224578]: Starting gazebo_ros_control plugin in namespace: /rrbot
[ INFO] [1387124767.978557316]: gazebo_ros_control plugin is waiting for model URDF in parameter [robot_description] on the ROS param server.

a second random error on startup is:

Msg Connected to gazebo master @
Msg Publicized address:
Exception [] Unable to start server[bind: Address already in use]. There is probably another Gazebo process running.
edit retag flag offensive close merge delete


What graphics card are you using?

SL Remy gravatar imageSL Remy ( 2014-01-05 17:55:09 -0500 )edit

I'm having the same problem. Happens frequently on all versions since I started using Gazebo about 18 months ago. This is a serious annoyance and wastes a lot of time. I've noticed it is even more frequent if other programs are continuously updating the screen (like performance monitor graphing). I'm running Ubuntu 12.04 on a generic PC. ATI Radeon HD 5450 graphics card.

BrianC gravatar imageBrianC ( 2014-01-17 13:07:12 -0500 )edit

What are the dimensions of the window that is being rendered? (I'm assuming this is the world file, or it's a default somewhere)

SL Remy gravatar imageSL Remy ( 2014-01-21 07:46:09 -0500 )edit

It takes a bit more work to try, but this problem may be solved in Gazebo 2.2.

nkoenig gravatar imagenkoenig ( 2014-03-04 19:26:44 -0500 )edit

2 Answers

Sort by ยป oldest newest most voted

answered 2014-01-24 18:10:39 -0500

BrianC gravatar image

Although it is not a real fix, I have recently discovered that gazebo crashes on startup much less often under ROS when you use debug mode. Just set the debug parameter when you launch gazebo, e.g.:

roslaunch gazebo_ros empty_world.launch debug:=true

It still crashes occasionally on startup but it has saved me a lot of time. I suspect the crash is due to a threading bug in ROS or Gazebo, and the debugger alters the timing enough that it is less likely to occur.

edit flag offensive delete link more


wtf haha, that actually works :P

jdddog gravatar imagejdddog ( 2014-02-27 19:41:41 -0500 )edit

answered 2014-01-05 18:03:06 -0500

SL Remy gravatar image

updated 2014-01-21 07:51:27 -0500

The first error may be related to the (graphics card) driver on your platform. One way to automate things a bit which will help to cope with the issue is to modify the node in the launch file and set respawn="True"

The second error is likely because the gazebo server is still running and has not yet been terminated. (shouldn't be an issue if the above change is made to the launch file)

This doesn't fix the original problem but it should help get Gazebo to start more smoothly for the user.

edit flag offensive delete link more
Login/Signup to Answer

Question Tools


Asked: 2013-12-15 10:29:27 -0500

Seen: 4,724 times

Last updated: Jan 24 '14