Opened 14 years ago
Closed 12 years ago
#1720 closed defect (invalid)
mapguide java memory leak
| Reported by: | cmy | Owned by: | |
|---|---|---|---|
| Priority: | low | Milestone: | 2.2 |
| Component: | AJAX Viewer | Version: | 2.0.2 |
| Severity: | trivial | Keywords: | memory leak |
| Cc: | External ID: |
Description
mapguide java memory leak
Change History (4)
comment:1 by , 14 years ago
comment:2 by , 14 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
closing as it's a duplicate of #1437 and no further information provided
comment:3 by , 12 years ago
| Resolution: | invalid |
|---|---|
| Status: | closed → reopened |
comment:4 by , 12 years ago
| Resolution: | → invalid |
|---|---|
| Status: | reopened → closed |
This is not a bug report.
You didn't specify your environment.
You didn't specify your steps for reproduction and what type of data was involved.
Not to mention 2.0.x series of MapGuide is way too old for any one of us to provide support.
Note:
See TracTickets
for help on using tickets.
can you reproduce this problem on mapguide 2.2?
please describe context of this leak in detail