Opened 16 years ago

Last modified 16 years ago

#25 closed defect (wontfix)

ST_Buffer crashes on WinXP, PostgreSQL 8.3, PostGIS 1.3.3

Reported by: nielslcr Owned by:
Priority: medium Milestone:
Component: postgis Version:
Keywords: Cc:

Description

I loaded data with FME from ArcSDE 9.2 to Postgis 1.3.3 ST_IsValid reports some invalid data, so I created a separate table with the invalid geometries. So far so good. If I try to fix the geometries with a 0 meter Buffer, PostGIS Crashes.

  1. update table set geom=st_buffer(geom, 0.0)
  2. attached are a screendump of the window that pops up and the log file
  3. I can provide a shapefile (or dump) of the data. zipped about 16MB

I am using PostgreSQL 8.3 on WinXP and Postgis 1.3.3 from stackbuilder: 'POSTGIS='1.3.3' GEOS='3.0.0-CAPI-1.4.1' PROJ='Rel. 4.6.0, 21 Dec 2007' USE_STATS'

The same process does work on WinXP, PostgreSQL 8.2.3, Postgis 1.3.2 'POSTGIS='1.3.2' GEOS='3.0.0rc4-CAPI-1.3.3' PROJ='Rel. 4.5.0, 22 Oct 2006' USE_STATS'

Change History (4)

comment:1 by mcayland, 16 years ago

Thanks for the bug report.

It looks like this is a GEOS assertion - what you will need to do is find the WKT for the geometry in question (i.e. find the exact geometry for which the buffer fails) and create a bug report on the GEOS bugtracker at http://trac.osgeo.org/geos/.

ATB,

Mark.

comment:2 by niels.hoffmann, 16 years ago

OK, Logged in the GEOS bugtracker as #187

Note: See TracTickets for help on using tickets.