Bug #2134

Concurrency Issue with Behavior Overwrite

Added by Alex Zirbel over 1 year ago. Updated over 1 year ago.

Status:FixedStart date:02/10/2013
Priority:NormalDue date:
Assignee:Yuyang Guo% Done:


Target version:-


In BehaviorGUI.py, if you run a new behavior, the rosnode kill used to stop the old behavior will often kill the newly running behavior, causing the new behavior to send a couple /set_motors commands but then die.

Known workaround: pausing and resuming the behavior does get the behavior running again.


#1 Updated by Yuyang Guo over 1 year ago

  • % Done changed from 0 to 100

#2 Updated by Priyanka Deo over 1 year ago

  • Status changed from Assigned to Fixed

Also available in: Atom PDF