Box2D, Box3D for curves regress failure between 2.1.8 and 2.2.0

[robe]

Testing in: PostgreSQL 9.4.4, compiled by Visual C++ build 1800, 64-bit

POSTGIS="2.1.8 r13780" GEOS="3.5.0-CAPI-1.9.0 r4088" PROJ="Rel. 4.8.0, 6 March 2012" GDAL="GDAL 1.11.1, released 2014/09/24" LIBXML="2.7.8" LIBJSON="UNKNOWN" RASTER

POSTGIS="2.2.0dev r14092" GEOS="3.5.0-CAPI-1.9.0 r4088" PROJ="Rel. 4.9.1, 04 March 2015" GDAL="GDAL 2.0.1, released 2015/09/15" LIBXML="2.7.8" LIBJSON="0.12" RASTER

SELECT Box2D('CURVEPOLYGON(CIRCULARSTRING(-71.0821 42.3036,-71.4821 42.3036,-71.7821 42.7036,-71.0821 42.7036,-71.0821 42.3036),(-71.1821 42.4036,-71.3821 42.6036,-71.3821 42.4036,-71.1821 42.4036))'::Geometry);

In 2.1.8 I get:

BOX(-71.7821 42.2622088907314,-71.0289871125841 42.9067128874151)

In 2.2.0 I get:

BOX(-71.7821 42.2622088907314,1.17549435082229e-038 42.9067128874151)

I'm very concerned about that - 1.17549435082229e-038 that seems to have come out of no where

[robe]

Same issue with box3d

SELECT Box3D('CURVEPOLYGON(CIRCULARSTRING(-71.0821 42.3036,-71.4821 42.3036,-71.7821 42.7036,-71.0821 42.7036,-71.0821 42.3036),(-71.1821 42.4036,-71.3821 42.6036,-71.3821 42.4036,-71.1821 42.4036))'::Geometry);

— 2.1.8 gives

BOX3D(-71.7821 42.2622088907314 0,-71.0289871125841 42.9067128874151 0)

— 2.2.0 gives

BOX3D(-71.7821 42.2622088907314 0,1.17549435082229e-038 42.9067128874151 0)

[pramsey]

Fixed at r14136