Bug #2134
Concurrency Issue with Behavior Overwrite
Start date:
02/10/2013
Due date:
% Done:
100%
Description
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.
History
#1 Updated by Yuyang Guo over 10 years ago
- % Done changed from 0 to 100
#2 Updated by Priyanka Deo over 10 years ago
- Status changed from Assigned to Fixed