Opened 18 years ago
Closed 15 years ago
#84 closed defect (fixed)
Mapping space line widths can cause extreme memory usage
| Reported by: | chrisclaydon | Owned by: | chrisclaydon |
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | Rendering Service | Version: | 1.2.0 |
| Severity: | critical | Keywords: | |
| Cc: | External ID: | 927942 |
Description
Use of a large mapping space line width can result in massive memory use, and ultimately in the server hanging.
When rendering we need to limit the width of rendered lines to the diagonal dimension of the screen, to prevent creation of HUGE rendering brushes that consume vast amounts of memory.
Change History (4)
comment:1 by , 18 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:2 by , 17 years ago
| Milestone: | → 1.3 |
|---|---|
| Resolution: | fixed |
| Status: | closed → reopened |
| Version: | → 1.2.0 |
Has been fixed for lines but has not yet been fixed for borders of areas.
comment:3 by , 17 years ago
| Milestone: | 2.0 |
|---|
comment:4 by , 15 years ago
| Resolution: | → fixed |
|---|---|
| Status: | reopened → closed |
Actualy borders of area were also fixed. In GDRenderer polylines and polygon borders are both drawn using the same code - WritePolylines.
The case that wasn't fixed was enhanced stylization - DrawScreenPolyline. I added the code to limit the line weight.
All GDRenderer code that allocates brushes now uses good sizes.
Note:
See TracTickets
for help on using tickets.
Fixed in 1.2.x by submission 1593, http://trac.osgeo.org/mapguide/changeset/1593
Fixed in trunk by submission 1594, http://trac.osgeo.org/mapguide/changeset/1594