ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

Time is out of dual 32-bit range

asked 2018-09-07 03:29:09 -0500

Felix Widmaier gravatar image

updated 2018-09-07 05:56:47 -0500

I am using ROS Kinetic on Ubuntu 16.04. After updating my system this morning (which included a lot of ROS packages), rosout and other nodes are crashing with the following exception:

terminate called after throwing an instance of 'std::runtime_error'
  what():  Time is out of dual 32-bit range

Minimal example to reproduce the issue:

  1. Run roscore in a terminal
  2. In another terminal run the following Python script:

    import rospy

When the script terminates rosout crash with the exception given above (in the roscore terminal)

If running more stuff, several other nodes crash with the same error.

Since everything was well yesterday, I suspect that this is caused by the update. Is anybody else having the same issue and/or knows how to fix it (apart from trying to roll back the update)?

edit retag flag offensive close merge delete


I tried to rollback the update but it seems that ROS packages of older versions are not kept in the apt repository, so apt-get is not able to install the old version.

Felix Widmaier gravatar image Felix Widmaier  ( 2018-09-07 04:43:32 -0500 )edit

I figured out it is not related to gazebo (apparently not even sim time). I updated the question with more minimal reproduction steps.

Felix Widmaier gravatar image Felix Widmaier  ( 2018-09-07 05:53:30 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted

answered 2018-09-07 06:33:42 -0500

Felix Widmaier gravatar image

It turned out I had some outdated clone of ros_comm in my workspace that apparently is incompatible with the latest update. Removing it from the workspace fixed the issue.

edit flag offensive delete link more



This was most likely an ABI compatibility issue.

Did you rebuild your workspace after installing updates?

Technically, you should. Most of the times it works without doing it, but if the updates changed the ABI, strange things like this may happen.

gvdhoorn gravatar image gvdhoorn  ( 2018-09-09 04:27:51 -0500 )edit

I did a complete clean & rebuild which did not help. The state of ros_comm I had in my workspace was pretty old, I think it just became incompatible with some other core package. I anyway don't need it anymore, though, so I am good with simply removing it from the workspace.

Felix Widmaier gravatar image Felix Widmaier  ( 2018-09-10 01:50:13 -0500 )edit

My "rebuild the workspace" statement was a bit ambiguous. What I meant to say is that after upgrading, rebuilding the workspace is essentially required.

Orthogonal to that: when ABI incompatibilities are introduced (either upstream or downstream), these sort of things can happen.

gvdhoorn gravatar image gvdhoorn  ( 2018-09-10 01:53:09 -0500 )edit

Question Tools



Asked: 2018-09-07 03:29:09 -0500

Seen: 5,291 times

Last updated: Sep 07 '18