#5684 closed defect (fixed)
Segfault from _RegisterMissingFaces
Reported by: | strk | Owned by: | strk |
---|---|---|---|
Priority: | blocker | Milestone: | PostGIS 3.5.0 |
Component: | topology | Version: | master |
Keywords: | Cc: |
Description
I'm getting a segfault from a draft implementation of TopoGeo_addGeometry which is pure plpgsql and shows the segfault happens when calling the internal _RegisterMissingFaces function which is instead written in C.
The C function is only accessible from 3.5.0dev (still unreleased) so I'm marking this as a blocker to avoid shipping a crashable version.
Attachments (1)
Change History (6)
comment:1 by , 10 months ago
by , 10 months ago
Attachment: | issue5684.pgtopo added |
---|
comment:2 by , 10 months ago
Instructions to reproduce:
- Download the attached issue5684.pgtopo
- Import with: pgtopo_import -f issue5684.pgtopo issue5684 | psql postgis_reg
- select topology._registermissingfaces('issue5684'); — 3 times
Here's the dance performance:
strk=# select topology._registermissingfaces('issue5684'); ERROR: Polygonize: face table is not empty. strk=# select topology._registermissingfaces('issue5684'); ERROR: Polygonize: face table is not empty. strk=# select topology._registermissingfaces('issue5684'); server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request. The connection to the server was lost. Attempting reset: Failed. The connection to the server was lost. Attempting reset: Failed. !?>
comment:4 by , 8 months ago
The fixing change was too wide in scope, introducing bug #5707. The change was reverted with [943215120c9fe63de0523f9560ca6a1a44e329aa/git] so I'm reopening this ticket as the fix needs to be somewhere else
In a6194d2/git: