#808 closed defect (fixed)
Many WMS requests to a MapGuide server causes Out of Memory and bad allocation errors
Reported by: | stevedang | Owned by: | stevedang |
---|---|---|---|
Priority: | high | Milestone: | 2.1 |
Component: | Rendering Service | Version: | 2.0.1 |
Severity: | major | Keywords: | |
Cc: | External ID: | 1146725 |
Description (last modified by ) ¶
Connect to MG WMS service using third party tool Gaia2. After adding one raster and one vector layer to a map, perform few zoom-in/out operations and MG server generates the error: "Out of memory, bad allocation".
This occurs frequently when the repository has a lot of resources; we had around 2000 in ours.
Change History (4)
comment:1 by , 16 years ago
Status: | new → assigned |
---|
comment:2 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
comment:3 by , 16 years ago
comment:4 by , 16 years ago
Description: | modified (diff) |
---|---|
Summary: | Repeated Zooming in/out to extents and Resample Raster puts MG server in Out of Memory state. → Many WMS requests to a MapGuide server causes Out of Memory and bad allocation errors |
Note:
See TracTickets
for help on using tickets.
Fixed by submission <<<http://trac.osgeo.org/mapguide/changeset/3560>>>.