[postgis-devel] [PostGIS] #518: Postgres backend terminated by exception 0xC0000005

[PostGIS]

#518: Postgres backend terminated by exception 0xC0000005
-----------------------+----------------------------------------------------
  Reporter:  loldrup   |       Owner:  pramsey                     
      Type:  defect    |      Status:  new                         
  Priority:  critical  |   Milestone:                              
 Component:  postgis   |     Version:  1.4.X                       
Resolution:            |    Keywords:  backend terminated exception
-----------------------+----------------------------------------------------
Comment (by pramsey):

 Right, there seems to be a dependency not only on particular data, but
 having them passed into the function in a particular order, which then
 (maybe?) creates a condition where the data is written past the bounds of
 the memory area and, if there are enough other processes running can hit
 something else and cause it to become invalid, which then causes a
 failure. At least, that's the guess. If we could get you to reproduce the
 error on a pgsql  that is compiled with --enable-cassert, we *might* see
 where the initial memory corruption occurs, instead of seeing the effect
 of it later on when the corrupt segment is then picked up by another
 process.

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/518#comment:12>
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.