[postgis-users] ST_AsSVG crashes with large/complex geometries

Mark Cave-Ayland mark.cave-ayland at siriusit.co.uk
Thu Feb 19 06:18:16 PST 2009

Mike Leahy wrote:

> Hello list,
> I'm wondering if anyone has run into issues with st_assvg locking up 
> postgresql.  I have an application that generates svg from unioned sets 
> of geometries.  So far it has been working pretty well, except I just 
> tested it with very large sets of geometries, and it invariably locks up 
> the backend database without any errors etc.  I could send a sample 
> geometry if that would help, but I think this can probably be done with 
> any dataset.  I've verified that the problem is not with st_union, as it 
> outputs a geometry just fine...it's only when it gets to st_assvg does 
> it freeze things...there is no CPU activity.  I do see this in the pg_log:
> *** glibc detected *** postgres: postgres testdb [local] SELECT: 
> realloc(): invalid next size: 0x000000000220f410 ***
> Am I just expecting too much of the st_assvg function, or is this 
> something that might be fixable?
> Thanks for any advice,
> Mike

Hi Mike,

Yeah, that sounds like a bug. What versions of PostgreSQL/PostGIS are 
you using? You may want to open a bug with a sample geometry on the 
PostGIS bugtracker.



Mark Cave-Ayland
Sirius Corporation - The Open Source Experts
T: +44 870 608 0063

More information about the postgis-users mailing list