We tried changing our renderer to GD because it wasn't causing the lock-ups that AGG is producing, and I thought that had solved our problems. With the release of MGOS 2.0, I wanted to test our maps to verify everything was working before we upgraded on our production machines, and I noticed that with the GD viewer, there is a large memory leak when zoomed in close and when the same problematic layer is visible. However, I went back and tested the map that I had included in Trac, and the problem does not show up. Also, I did note, though, that when I zoom in to an area that is located outside the bounds of a polygon like the one in the Trac example, the memory leak doesn't occur; it only occurs when zooming in inside of similar polygons.
J Manafi wrote: > > I have experienced extremely long refresh rates when the zoom scale is > really low (~1:33 or so). The time it takes to refresh for the Sheboygan > example is at least 10x normal, and on a custom map, MapGuide server > pretty much hangs at ~1:250 (currently sitting and waiting). Has anyone > else noticed this behavior at low scales? > -- View this message in context: http://www.nabble.com/map-refresh-timeout-tp15442680s16610p15836576.html Sent from the MapGuide Users mailing list archive at Nabble.com.
_______________________________________________ mapguide-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapguide-users
