For an infinite region, no region bounds can be computed:

Default values for the bounding box will be used. The issue is best addressed by specifying explicit numerical bounds:

Inspect the bounds:

Sometimes, the region bounds computation takes too long and the algorithm bails out. In that case, the message can be generated even for a region that has bounds. Consider the following region:

The algorithm fails to compute region bounds and uses the default bounds:

One can explicitly compute the region bounds:

Alternatively, one can compute the bounds of the individual pieces and find the extent of those:

And use those bounds in the computation:

An alternative is to manually specify bounds that are possibly too large:

In that case, pay attention that the boundary is resolved sufficiently well:

In this case, another alternative is to specify the region symbolically. Generally speaking, specifying the region symbolically will give the most accurate representation of the region:

This message can be generated by other functions:

The result is based on a region with the default bounds. Specifying region bounds addresses the issue:

If the region's bounds cannot be computed, system default values specified through the "DefaultBounds" option will be used:

The default values can be modified with a system option:

Inspect the bounds:

Restore the original default values: