Opened 12 years ago
Closed 11 years ago
#1977 closed defect (fixed)
Segfault on ST_Intersection
Reported by: | andrepl | Owned by: | strk |
---|---|---|---|
Priority: | critical | Milestone: | PostGIS GEOS |
Component: | postgis | Version: | 2.0.x |
Keywords: | st_intersection segfault | Cc: | andrepl |
Description
I'm receiving a segfault performing st_intersects on the 2 geometries included in the attached file.
Attachments (2)
Change History (17)
by , 12 years ago
comment:1 by , 12 years ago
Cc: | added |
---|
comment:2 by , 12 years ago
andrepl,
This isn't crashing for me on my PostGIS 2.0.1 nor PostGIS 2.1.0 instances.
I ran:
select st_intersects(g,g2) from reduce;
and returned true.
Can you please provide the output of the following query:
select version() || ' ' || postgis_full_version();
It's also possible that the geometry is malformed in the database but fixes itself when it goes thru the output process. I've had a case like that happen to me.
To test, you can reload the dump you have here into a new database and see if it crashes.
comment:3 by , 12 years ago
Keywords: | st_intersection added; st_intersects removed |
---|---|
Summary: | Segfault on ST_Intersects → Segfault on ST_Intersection |
Apologies, I meant to write ST_Intersection, not ST_Intersects. I updated the title of the ticket but I'm not sure if I can change the description…
running "select st_intersection(g,g2) from reduce" segfaults for me with this setup:
PostgreSQL 9.1.4 on x86_64-unknown-linux-gnu, compiled by gcc-4.4.real (Debian 4.4.5-8) 4.4.5, 64-bit POSTGIS="2.0.2SVN r10189" GEOS="3.3.5-CAPI-1.7.5" PROJ="Rel. 4.8.0, 6 March 2012" GDAL="GDAL 1.9.1, released 2012/05/15" LIBXML="2.7.8" LIBJSON="UNKNOWN" RASTER
comment:4 by , 12 years ago
Great always good to be able to reproduce the problem. It segfaults for me under both my 64-bit and 32-bit PostgreQL 9.1 PostGIS 2.0.1 and 2.1.0SVN installs.
comment:5 by , 12 years ago
Owner: | changed from | to
---|
This crashes for me in GEOS 3.3.5 and 3.3.4 but works in 3.3.2.
comment:7 by , 12 years ago
Milestone: | PostGIS 2.0.2 → PostGIS GEOS |
---|
comment:9 by , 12 years ago
It's fixed in GEOS-3.3 branch (to become 3.3.6). Out of curiosity: are you running robustness tests ? I ask because the linear geometry is extremely scratchy, can't be any real physical feature, is it ?
by , 12 years ago
Attachment: | bug586_line.png added |
---|
comment:12 by , 12 years ago
Robe, see the geos ticket for geos-related questions (both 3.3 and 3.4 were affected and both were fixed).
andrepl, weird tracks come out of those GPS:
I didn't try but I suspect that multiline might have other problems with other operations, worth stress-testing
This ticket will be closed as soon as GEOS-3.3.6 is out
comment:13 by , 12 years ago
The wierd tracks are caused by the gps 'drifting' while the device is stationary. we pass the data through a douglas-peucker algorithm and that's the result… it's not pretty, and has been a real hassle to fully filter out while still getting accurate tracks.
comment:14 by , 12 years ago
strk — I have bad news for you — my GEOS regress tests are failing (at least on my local pc where they all used to pass). It something like 30 failures out of those 3000 someodd xmltests. I think this is a new development. I'll try to narrow it down a bit more.
comment:15 by , 11 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Not only GEOS-3.3.6 was released, but up to GEOS-3.3.9, and GEOS 3.4.2. Can anyone still reproduce this ? Reopen if so.
geometries which segfault st_intersects