Skip to content
This repository has been archived by the owner on Feb 3, 2025. It is now read-only.

Assert in pull request #310 kills drcsim after 15 seconds #529

Closed
osrf-migration opened this issue Feb 26, 2013 · 9 comments
Closed

Assert in pull request #310 kills drcsim after 15 seconds #529

osrf-migration opened this issue Feb 26, 2013 · 9 comments
Labels
all bug Something isn't working major

Comments

@osrf-migration
Copy link

Original report (archived issue) by Steve Peters (Bitbucket: Steven Peters, GitHub: scpeters).


Gazebo pull request #310 introduces some GZ_ASSERT's into the sensor manager. I approved it, but I should have tested it with drcsim, because gazebo is exiting after about 15 seconds of sim time when running roslaunch atlas_utils atlas_drc_vehicle_firehose.launch. We should probably change that to a gzerr or gzwarn for the time being.

***** Internal Program Error - assertion (eventTime >= common::Time::Zero) failed in void 
gazebo::sensors::SensorManager::SensorContainer::RunLoop():
/home/scpeters/osrf/gazebo2/gazebo/sensors/SensorManager.cc(467): 
Time to next sensor update is negative.
@osrf-migration
Copy link
Author

Original comment by Jose Luis Rivero (Bitbucket: Jose Luis Rivero, GitHub: j-rivero).


Question is: is this really an error catch by assertion? or the assertion should not be in this place at all? Are we proposing a workaround by relaxing the assertion?

@osrf-migration
Copy link
Author

Original comment by Steve Peters (Bitbucket: Steven Peters, GitHub: scpeters).


It seems risky to make it an assertion to me, since it's related to timing of multiple threads. I think it should just be a warning message.

@osrf-migration
Copy link
Author

Original comment by Steve Peters (Bitbucket: Steven Peters, GitHub: scpeters).


I've done some debugging with printf, and the sensor container that triggers the assert is the one containing the imu_sensor. I've printed out startTime, diffTime, sleepTime, and eventTime:

Time to next sensor update is negative.
imu_sensor
startTime 12 618000000
diffTime 0 3000000
sleepTime 0 1000000
eventTime 0 -2000000
Time to next sensor update is negative.
imu_sensor
startTime 12 819000000
diffTime 0 2000000
sleepTime 0 1000000
eventTime 0 -1000000
Time to next sensor update is negative.
imu_sensor
startTime 13 668000000
diffTime 0 2000000
sleepTime 0 1000000
eventTime 0 -1000000

@nkoenig Does this seem like an atlas/drcsim problem or a gazebo problem?

@osrf-migration
Copy link
Author

Original comment by Steve Peters (Bitbucket: Steven Peters, GitHub: scpeters).


Issue #535 was marked as a duplicate of this issue.

@osrf-migration
Copy link
Author

Original comment by Nate Koenig (Bitbucket: Nathan Koenig).


Accidentally pushed a fix into default. Take a look at it here:

https://osrf-migration.github.io/gazebo-gh-pages/#!/osrf/gazebo/commits/0ddd1f60a8cd5411ba328f5c6265f4a2f9a3f98e (1f06de6)

@osrf-migration
Copy link
Author

Original comment by Steve Peters (Bitbucket: Steven Peters, GitHub: scpeters).


Looks good.

@osrf-migration
Copy link
Author

Original comment by Steve Peters (Bitbucket: Steven Peters, GitHub: scpeters).


  • changed state from "new" to "resolved"

fixed in 1f06de6

@osrf-migration
Copy link
Author

Original comment by Nate Koenig (Bitbucket: Nathan Koenig).


  • set version to "all"

@osrf-migration
Copy link
Author

Original comment by Nate Koenig (Bitbucket: Nathan Koenig).


  • changed state from "resolved" to "closed"

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
all bug Something isn't working major
Projects
None yet
Development

No branches or pull requests

1 participant