[mapserver-users] mapscript.jar in java

[Umberto Nicoletti]

Please note that growing memory usage is not necessarily symptom of a
problem. On the other hand memory not being released IS a problem.

Invoking programmatically the garbage collector does nothing towards
addressing memory leaks and, almost certainly in both cases, will
reduce the overall JVM performance.

As far as memory leaks are concerned Mapserver/Mapscript should be
mostly leak free, but ymmv depending on the features you are using.
If you are afraid (or know) that mapscript is leaking memory please
run it through Valgrind, then open an issue with both a test case and
a Valgrind output.

Best regards,
Umberto


On Tue, Sep 11, 2012 at 4:30 PM, Gaston Lucero <gaston.lucerom at gmail.com> wrote:
>
> I use System.gc() before  map.Draw() And the memory remains stable,
> Currently I use Java 7, but earlier in java 6 also works
> System.gc has several improvements in Java 7, you should try it
>
> _______________________________________________
> mapserver-users mailing list
> mapserver-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapserver-users
>