Thank you both. Unfortunately I'm using MapGuide 32 bit. I will look into it.
--
Sent from: http://osgeo-org.1560.x6.nabble.com/MapGuide-Users-f4182607.html
___
mapguide-users mailing list
mapguide-users@lists.osgeo.org
I can definitely confirm that rendering large map images via the API is
definitely memory intensive on the Mapguide site. Then when you get the
image out into .NET, you might even go into deeper problems with the way the
Large Object Heap collection works and so on. You can end up with pretty
I can tell you right now, if you're expecting a 80MB png to be rendered, it
will not take 80MB of memory to render said PNG. It takes much much more
memory.
I did a little test just to see how much memory is being used to render the
Sheboygan sample map at full map extents with an image size of
It's DIN A2, so I pass 9922 x 14032 pixel to that function. I'm not sure why
that's too much, if I'm not wrong then 9922 x 14032 pixel is something about
80 MB for a PNG.
--
Sent from: http://osgeo-org.1560.x6.nabble.com/MapGuide-Users-f4182607.html
What kind of image sizes are you dealing with here out of curiosity?
- Jackie
--
Sent from: http://osgeo-org.1560.x6.nabble.com/MapGuide-Users-f4182607.html
___
mapguide-users mailing list
mapguide-users@lists.osgeo.org
Hello I'm using MapGuide v.2.5.2.7949 in an ASP.NET Application.
I'm facing an out of memory exception throwed by this function (RenderMap):
http://cmnmaps.ca/mapguide/help/webapi/de/dbd/class_mg_rendering_service_a7767628fe456bfd90e9010a19ed83e04.htm#a7767628fe456bfd90e9010a19ed83e04
In my App
