[gradsusr] Memory Allocation Error When Using PRINTIM

[Stephen McMillan]

Arllindo, Jennifer,
Obviously the choice of shapefiles and output image dimensions play a
critical part, not to mention the GrADS version you mentioned.  Still using
2.0.a7.oga.3, by replacing one shapefile for just the Alaska portion, I was
able to "printim" an image without the memory allocation error.  In this
case, I replaced the shapefile "ln_ak" with "admin98 2342" for AK.  However,
if I tried to output a higher-resolution image (say, x1440 y1080), GrADS
simply crashed (I briefly saw an error about something being corrupted).  I
can do 960x720 or 1200x900 without a problem.

I have win32 superpack 2.0.a9.oga.1 on my other machine at home, so I'll try
the original script on that this evening.  That could be interesting, since
it's about a 10-years-old Windows XP laptop with much less RAM (500MB?).
 For now, I'd rather not attempt the COLA version 2.0.a9, since I ran into
problems trying to install it several weeks ago.  Perhaps someone else with
a9 would like to give it a shot.

Thanks for your comments and suggestions!
Stephen

On Wed, Dec 1, 2010 at 8:07 PM, Arlindo da Silva <dasilva at alum.mit.edu>wrote:

>
>
> On Wed, Dec 1, 2010 at 7:59 PM, Jennifer Adams <jma at cola.iges.org> wrote:
>
>> Hi, Stephen --
>> The error message you're seeing occurs when the printim code tries to
>> allocate an array that contains the vertices of a filled polygon. It may be
>> that your shapefiles have single polygons with so many vertices (e.g. the
>> one that fills in most of Canada) that your 3.2Gb of RAM is not enough, or
>> maybe an integer isn't big enough to represent the number of elements in the
>> array, so it passes malloc some junk and you get an error. To complicate
>> things, you are also using a deprecated shapefile interface that I didn't
>> write.
>>
>> See if you can reliably reproduce this error with the latest COLA version
>> of GrADS. If so, then send me the simplest possible script and the required
>> shapefiles, and I will try to reproduce the error on my own system that has
>> lots and lots of available memory.
>>
>
> I agree, the new shapefile interface is the way to go. The latest win32
> superpack 2.0.a9.oga.1 has exactly the same shapefile code that Jennifer
> wrote, you could try that as well.
>
>    Arlindo
>
>
> --
> Arlindo da Silva
> dasilva at alum.mit.edu
>
> _______________________________________________
> gradsusr mailing list
> gradsusr at gradsusr.org
> http://gradsusr.org/mailman/listinfo/gradsusr
>
>

***************************************************
The information contained in this e-mail message 
is intended only for the use of the recipient(s) 
named above and may contain information that is 
privileged, confidential, and/or proprietary. 
If you are not the intended recipient, you may not
review, copy or distribute this message. If you have
received this communication in error, please notify 
the sender immediately by e-mail, and delete the original message.
***************************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://gradsusr.org/pipermail/gradsusr/attachments/20101202/d8687660/attachment-0003.html