Default clipping values are incorrect when the data frame uses a projected coordinate system

Description

A data frame is currently set to a projected coordinate system, and data frame clipping is selected by enabling Clip to Shape in the Data Frame Properties dialog box. The default values for the custom extent clipping bounds seem incorrect, especially when the Degrees option is checked. When accepting these values, ArcMap fails to respond, it seems to go into a loop and eventually uses all the available memory.

Cause

The clipping dialog box allows you to specify clip bounds in either decimal degrees or projected units. If the data frame uses a projected coordinate system, the clipping dialog box doesn't use an inverse project to convert the projected units to degrees; instead, the source code tries to translate the map units.

Solution or Workaround