[mapguide-internals] Huge memory leaks in Mapguide Exceptions

Bruno Scott bscott at geomapgis.com
Thu Jul 9 10:05:44 EDT 2009

I have found the problem causing Mapguide to loose 4 Meg / minutes on a 20
concurent users stress test.

When you have that type of exception in your error log

Error: An exception occurred in FDO component. Unable to find class
Error: Resource was not found: Session:...//Sheboygan.Map

Mapguide loose a lot of memory. Without fixing the problem i got this Out of
memory exception in 5 minutes

The memory leak itself is a problem, but the biggest problem is from our
client. Even if they name themself administrator they are not. And it is not
clear that this type of error could make Mapguide really unstable under
stress conditions.

First thing would be to include a warning in the MapGuide Best Practices:
  "Exception can cause memory leaks"
  "Periodically check your error log"
  "Test your Map at all scales after any modification and verify if
everithing is OK in the log file"

A better way would be to warned the administrator right in the studio as
soon as an exception happend.


View this message in context: http://n2.nabble.com/Huge-memory-leaks-in-Mapguide-Exceptions-tp3231610p3231610.html
Sent from the MapGuide Internals mailing list archive at Nabble.com.

More information about the mapguide-internals mailing list