[postgis-tickets] [PostGIS] #2995: invalid access to memory location

[PostGIS]

#2995: invalid access to memory location
------------------------+---------------------------------------------------
 Reporter:  robe        |       Owner:  robe         
     Type:  defect      |      Status:  new          
 Priority:  high        |   Milestone:  PostGIS 2.1.6
Component:  postgis     |     Version:  2.1.x        
 Keywords:  windows 64  |  
------------------------+---------------------------------------------------
Description changed by robe:

Old description:

> 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 R1 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
> }}}

New description:

 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
 }}}

--

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/2995#comment:4>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.