Opened 12 months ago

Closed 12 months ago

Last modified 12 months ago

#5626 closed defect (fixed)

ST_LargestEmptyCircle crashes on GEOS 3.13 with Triangle

Reported by: robe Owned by: pramsey
Priority: medium Milestone: PostGIS GEOS
Component: postgis Version: 3.4.x
Keywords: Cc:

Description (last modified by robe)

SELECT ST_LargestEmptyCircle('POINT(-11.1111111 40)'::geometry
       ,20.1
      , 'TRIANGLE((-71.0821 42.3036,-71.0821 42.3936
          ,-71.0901 42.3036,-71.0821 42.3036))'::geometry )
POSTGIS="3.5.0dev 3.4.0rc1-806-g59aba6dcb" 
[EXTENSION] PGSQL="160" GEOS="3.13.0dev-CAPI-1.18.0" SFCGAL="SFCGAL 1.5.0, CGAL 5.6, BOOST 1.78.0" PROJ="8.2.1 NETWORK_ENABLED=OFF 
URL_ENDPOINT=https://cdn.proj.org 
USER_WRITABLE_DIRECTORY=C:\Users\lr\AppData\Local/proj 
DATABASE_PATH=C:\ming64gcc81\projects\proj\rel-proj-8.2.1w64gcc81/share/proj/proj.db" LIBXML="2.9.14" LIBJSON="0.12" LIBPROTOBUF="1.2.1" WAGYU="0.5.0 (Internal)"

berrie64 which also does crasher tests seems to have gone thru fine (though I just checked and she's only testing GEOS 3.12.0 so have to up that), so maybe this only affects GEOS 3.13.

I'm running with a week old geos, and will test after my latest is rebuilt.

I'm surprised GEOS even works with triangles. When did this happen. Should it be erroring out, or does GEOS now support triangles?

Change History (7)

comment:1 by robe, 12 months ago

Description: modified (diff)

comment:2 by pramsey, 12 months ago

Triangle is just a really simple polygon, so I bet we're just flipping the type.

comment:3 by pramsey, 12 months ago

Not a triangle problem, something gnarlier. This crashes.

SELECT ST_LargestEmptyCircle('POINT(-11.1111111 40)'::geometry
       ,20.1
      , 'POLYGON((-71.0821 42.3036,-71.0821 42.3936
          ,-71.0901 42.3036,-71.0821 42.3036))'::geometry );

comment:5 by robe, 12 months ago

I just tested this against GEOS 3.12.2dev (built yesterday) and no crash on that, so seems to be an new issue in 3.13

comment:6 by robe, 12 months ago

Resolution: fixed
Status: newclosed

This issue was introduced in GEOS 3.13 which is not yet released yet and has been fixed now in GEOS 3.13

comment:7 by robe, 12 months ago

Milestone: PostGIS 3.5.0PostGIS GEOS
Note: See TracTickets for help on using tickets.