[postgis-devel] Re: [postgis-users] Performance and memory problems

[strk]

I narrowed it down to this:

SELECT buffer('GEOMETRYCOLLECTION(POLYGON((709150 160666,709150 160669,709151
160666,709150 160666)),POLYGON((709150 160664,709151 160665,709156
160636,709150 160664)),POLYGON((709116 160646,709117 160646,709141
160627,709116 160646)),POLYGON((709072 160619,709114 160645,709115
160645,709072 160619)),LINESTRING(709151 160665,709151
160665),LINESTRING(709141 160627,709141 160627),LINESTRING(709139
160686,709150 160669),LINESTRING(709119 160672,709139
160686),LINESTRING(709115 160645,709115 160645),LINESTRING(709092
160677,709119 160672),LINESTRING(709059 160668,709092
160677),LINESTRING(709038 160655,709059 160668),LINESTRING(709025
160610,709025 160610),LINESTRING(709011 160631,709038
160655),LINESTRING(709011 160631,709011 160631))', 0);

Bang! Signal 11.

good luck !

--strk;


dblasby wrote:
> > valgrind on postgres with palloc/pfree/repalloc made macros
> > to malloc/free/realloc suggests a problem in add_to_geometry.
> 
> I thought it might be there.  Can you get the crash to be re-producable 
> with something like simple like:
> 
>  >>SELECT buffer(<bad geometry>,0) ;
>  >>
>  >>and
>  >>
>  >>SELECT geomunion(<bad geometry>,<bad geometry>);
> 
> If so, I can probably take a look at why its having problems.
> 
> 
> dave
> 
> 
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-devel