Opened 10 years ago
Last modified 7 years ago
#2995 closed defect
invalid access to memory location — at Version 4
Reported by: | robe | Owned by: | robe |
---|---|---|---|
Priority: | high | Milestone: | PostGIS 2.1.7 |
Component: | postgis | Version: | 2.1.x |
Keywords: | windows 64 | Cc: | dbaston |
Description (last modified by )
This may be a duplicate of #2476 and could even be a windows 64 specific issue. I'm not tagging it as raster this time though cause I'm not sure its raster.
Leo has managed to trigger this error:
invalid access to memory location
To be a bit annoying. One is a nightly process he runs which he was able to get around the issue by changing the order of the steps in his process. The only thing odd about his process is his unorthodox use of PostGIS (converting times to geometries so he could use geometry intersection and aggregate functions).
The other was just geocoding some data.
Neither invoived using any raster functions. I haven't quite pinpointed what could be the issue, but he's managed to trigger the problem on two separate Windows 64-bit boxes (one running Windows 2012 R2 and another Windows 2008 R2)
But same version of PostgreSQL / PostGIS:
POSTGIS="2.1.3 r12547" GEOS="3.4.2-CAPI-1.8.2 r3924" PROJ="Rel. 4.8.0, 6 March 2012" GDAL="GDAL 1.10.0, released 2013/04/24" LIBXML="2.7.8" LIBJSON="UNKNOWN" RASTER PostgreSQL 9.3.5, compiled by Visual C++ build 1600, 64-bit
Change History (4)
comment:1 by , 10 years ago
Owner: | changed from | to
---|
comment:2 by , 10 years ago
Milestone: | PostGIS 2.1.5 → PostGIS 2.1.6 |
---|
comment:3 by , 10 years ago
comment:4 by , 10 years ago
Description: | modified (diff) |
---|
I think upgrading my build chain to gcc 4.8.3 might have fixed the issue. I shipped PostgreSQL 9.3 and 9.4 (PostGIS 2.1.5 with newer gcc build) and the job in question haven't been failing since we upgraded.
Leaving it open until further investigation.