Revision history [back]

Calling clear costmaps at a high rate is probably not tested -- as it is not a common use case. Typically this service is called only periodically when there is too much garbage in the costmaps. If you find yourself calling this frequently, you might want to look at why, and figure out what in your use case causes you to do this.

You might also file a ticket and/or open a pull request if you find a solution to the segfault.