Revision history [back]

Sidd is correct. The costmap aims to keep the map up to date with the most recent information it got. If it sees obstacles and then moves away without clearing them, it will keep that information forever (or until new sensor data clears the obstacles).

If this causes no path to be found, the recovery behaviors should trigger to clear the obstacles.

If you wish not to remember this data at all, you can remove the obstacles layer from your global costmap, and the obstacle layer in the local costmap will keep you from hitting obstacles.