Linking possibly related issue 824.
While not directly connected, both are about identification problems at the same
place (except one ended with a crash, and another one ended with an event not
triggering)

There is a possibility the bug is related to the obstacles itself and I'm not
looking at the right place (as in: cmp_obstacle_state may be innocent), so I'm
linking both issues for further analysis and study.