Mauro Bartolomeoli ha scritto: > Testing GeoServer 1.7.5, I found a strange behaviour in WMS: when the > requested bounding box is little (10 to 50 meters) in comparison to the > requested featuretype/s bbox (some kilometer to hundreds of kilometers). > Memory used starts to grow during rendering until I get an OutOfMemory. > The same featuretypes were rendering perfectly (with low memory usage) > on 1.7.3a. > > Maybe the bug is related to GEOS-3162. It seems that when a shape is > much bigger than the requested area it cannot be rendered anymore using > limited resources. > To reproduce the bug try the following request: > http://localhost:8080/geoserver/wms?bbox=-100,35,-99.999,35.0001&styles=population&Format=image/png&request=GetMap&layers=topp:states&width=550&height=250&srs=EPSG:4326
Is this happening also if you don't provide any stroke in the polygon symbolizers? (sorry I did not test that myself, I'm on the hook for some other work) Cheers Andrea -- Andrea Aime OpenGeo - http://opengeo.org Expert service straight from the developers. ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
