SMACH slows down after hours of execution of large FSM on PR2
When I run my SMACH code on the PR2 for a long time, about 90 minutes or more, it slows down considerably. Everything is in one giant (albeit nested) SMACH fsm with about 125 states. The slowdown affects everything in the (python) process, including state transitions and all other bits of code. When running top I don't see any big CPU or memory usage increase.
Have you guys run into this on your SMACH codes? I've been bumping into this more and more as the code crashes less often (meaning longer code runtimes). Restarting the robot (both hardware and software) does not seem to prevent this from happening again.
This happens even when smach_viewer is not running.