[be sure to reply to ncl-talk and not to me directly, so that other
members of the community can benefit and offer suggestions if they have any]
Hi Lisa,
It's probably not the specific cause, unless some other script is
calling this script as a function, but it still couldn't hurt to try
that (and it's usually good programming practice to do that anyway).
What's almost certain is that somehow you're getting an array that's too
large for your computer's memory to handle. So if the simple things
such as cleaning up/deleting variables doesn't help, I'd suggest
thinking about if there's another way you can break up your data
processing (loops? subsetting your data? writing your data to file?) so
that you don't have such huge array(s) being stored in memory or being
operated upon. Going from the information you've sent so far, I don't
really have anything more specific to suggest at this point.
Jared
On 03/26/2014 01:26 PM, Lisa Alexander wrote:
> Hi Jared,
>
> Thanks for the input. In the program I don't delete any of the variables, because they are all overwritten on each consecutive loop (the values are all found again). Do you figure this would cause the problem?
>
> Thanks,
> Lisa
> --------------------------------------------
> On Wed, 3/26/14, Jared Lee <jaredlee@ucar.edu> wrote:
>
> Subject: Re: Fatal Error Message
> To: ncl-talk@ucar.edu
> Received: Wednesday, March 26, 2014, 3:21 PM
>
> Lisa,
>
> Your script definitely has a problem with memory. My
> first guess is
> that it has an array to which elements are being added in a
> loop, which
> eventually becomes so large that its memory requirements
> exceed that of
> your computer. Either that, or you're trying to read
> in large
> multidimensional arrays from hundreds of files at
> once. Or you could
> potentially have a memory leak somewhere in your script,
> which can
> sometimes be caused by not deleting variables when they're
> no longer
> necessary. One of those possibilities has typically
> been the cause of
> similar situations that I've experienced in the past.
>
> Jared
>
>
> On 03/26/2014 12:56 PM, Lisa Alexander wrote:
> > Hello,
> > I have been running a program on my computer, but this
> time the case time length is very long. When I run it, it
> stops part way through and gives me this message:
> >
> > fatal:NclMalloc Failed:[errno=12]
> > Segmentation fault (core dumped)
> >
> > I must say, whenever I run the program (this time and
> other times), the program runs very quickly to begin with,
> but slows down over time.
> >
> > Can somebody let me know what the error message means?
> > Thanks,
> > Lisa
> > _______________________________________________
> > ncl-talk mailing list
> > List instructions, subscriber options, unsubscribe:
> > http://mailman.ucar.edu/mailman/listinfo/ncl-talk
>
> --
> ================
> Dr. Jared A. Lee
> Postdoctoral Research Scientist
> National Center for Atmospheric Research
>
> Phone: 303.497.8485
> Email: jaredlee@ucar.edu
> Web: https://staff.ucar.edu/users/jaredlee
> ================
>
> _______________________________________________
> ncl-talk mailing list
> List instructions, subscriber options, unsubscribe:
> http://mailman.ucar.edu/mailman/listinfo/ncl-talk
>
-- ================ Dr. Jared A. Lee Postdoctoral Research Scientist National Center for Atmospheric Research Phone: 303.497.8485 Email: jaredlee@ucar.edu Web: https://staff.ucar.edu/users/jaredlee ================ _______________________________________________ ncl-talk mailing list List instructions, subscriber options, unsubscribe: http://mailman.ucar.edu/mailman/listinfo/ncl-talkReceived on Wed Mar 26 13:42:35 2014
This archive was generated by hypermail 2.1.8 : Mon Mar 31 2014 - 11:47:09 MDT