Opened 12 years ago

Closed 11 years ago

#582 closed defect (fixed)

GEOSGetCentroid seg faults on certain MultiPolygons

Reported by: dazuma Owned by: strk
Priority: blocker Milestone: 3.3.9
Component: Default Version: 3.3.4
Severity: Critical Keywords: history 3.3.8
Cc:

Description

Consider the following MultiPolygon:

MULTIPOLYGON(EMPTY, ((0 1, 1 1, 1 0, 0 0, 0 1)))

I'm not completely clear on whether this should be considered a valid MultiPolygon. Most calls handle it fine. However, calling GEOSGetCentroid_r on it results in a segmentation fault.

The seg fault seems to happen when the MultiPolygon contains at least one EMPTY polygon *and* at least one non-empty polygon. MultiPolygons containing only EMPTYs or only non-emptys work fine.

Change History (6)

comment:1 by strk, 12 years ago

Milestone: 3.3.5 → 3.3.6
Severity: Unassigned → Critical

comment:2 by strk, 11 years ago

Milestone: 3.3.6 → 3.3.7
Priority: major → blocker

comment:3 by strk, 11 years ago

Milestone: 3.3.7 → 3.3.x

comment:4 by strk, 11 years ago

Owner: changed from geos-devel@… to strk
Status: new → assigned

I'm on it.

comment:5 by strk, 11 years ago

Keywords: history 3.3.8 added

r3773 in trunk, r3774 in 3.3 branch

comment:6 by strk, 11 years ago

Resolution: → fixed
Status: assigned → closed
Note: See TracTickets for help on using tickets.