| HELP> Unable to allocate memory: to make array. [message #1014] |
Fri, 28 May 1993 12:35  |
burel
Messages: 2
Registered: August 1992
|
Junior Member |
|
|
HELP!
I am trying to do an FFT on a large image (6000x6000 byte) and about
20 minutes into the procedure I get this error:
% Unable to allocate memory: to make array.
Not enough space
Is this a PV-Wave problem or a procedure problem? I'm running PV-Wave 4.01
on an SGI 340 VGX with 256 Meg RAM and 338 MB Swap (694040 blocks) What can
I do to get around this problem?
Thanks for any help
Jon
--
========= Jonathan Burelbach (burel@highwire.gsfc.nasa.gov) ========
NASA / Goddard Space Flight Center Phone: (301) 286-6166
MODIS Characterization Support Team Fax: (301) 286-9200
Code 925
Greenbelt, MD 20771
|
|
|
|
| Re: % Unable to allocate memory: to make array. [message #8500 is a reply to message #1014] |
Fri, 21 March 1997 00:00  |
steinhh
Messages: 260
Registered: June 1994
|
Senior Member |
|
|
In article <5grkoh$etm@post.gsfc.nasa.gov>, thompson@orpheus.nascom.nasa.gov (William Thompson) writes:
|> davidf@dfanning.com (David Fanning) writes:
|>
|> >buzzcut <buzzcut@highland.com> wrote:
|>
|> >> Are there anyways around this error besides .size 65000 65000?
|> >> Any useful tips?
|> >>
|> >> % Unable to allocate memory: to make array.
|> >> not enough core
|>
|> >Allocate more virtual memory to your IDL process.
|>
|> I don't believe that the .size command is relevant to the "not enough core"
|> error message. As I understand it, this cannot be solved at the user level,
|> but must be addressed at the system manager level. Either one needs to create
|> more swap space, or increase the user's quota if the machine uses process
|> quotas. I know that the latter is true on VMS systems, but I don't think it's
|> generally true under Unix. I don't know about Windows or MacOS.
|>
Under e.g., Digital UNIX, this problem may also be artificially imposed on
a process by software limits on memory use, maintaned by the user's shell - e.g.,
unix> limit
cputime unlimited
filesize unlimited
datasize 131072 kbytes
stacksize 2048 kbytes
coredumpsize 0 kbytes
memoryuse 90200 kbytes
vmemoryuse 1048576 kbytes
descriptors 4096
The limits may be changed by e.g.,
unix> limit datasize 1024m
which gives the child processes an allowed data size of 1 Gbyte.
I'd also like to point out the use of the coredumpsize, which disallows
any core dumps when set to zero - how often do you actually *use* those
humongous files, anyway....
Stein Vidar Haugan
|
|
|
|
| Re: % Unable to allocate memory: to make array. [message #8503 is a reply to message #8500] |
Thu, 20 March 1997 00:00 |
David Foster
Messages: 341
Registered: January 1996
|
Senior Member |
|
|
buzzcut wrote:
>
> Are there anyways around this error besides .size 65000 65000?
> Any useful tips?
>
> % Unable to allocate memory: to make array.
> not enough core
Supposedly IDL 5.0 is removing these restrictions. Does that
command really prevent your error? If so, you must be exceeding
the amount of space available for the symbol table in the data
area of your program, something I've never seen except at the
$MAIN level.
Dave
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~
David S. Foster Univ. of California, San Diego
Programmer/Analyst Brain Image Analysis Laboratory
foster@bial1.ucsd.edu Department of Psychiatry
(619) 622-5892 8950 Via La Jolla Drive, Suite 2200
La Jolla, CA 92037
[ UCSD Mail Code 0949 ]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~
|
|
|
|
| Re: % Unable to allocate memory: to make array. [message #8511 is a reply to message #8500] |
Thu, 20 March 1997 00:00 |
thompson
Messages: 584
Registered: August 1991
|
Senior Member |
|
|
davidf@dfanning.com (David Fanning) writes:
> buzzcut <buzzcut@highland.com> wrote:
>> Are there anyways around this error besides .size 65000 65000?
>> Any useful tips?
>>
>> % Unable to allocate memory: to make array.
>> not enough core
> Allocate more virtual memory to your IDL process.
I don't believe that the .size command is relevant to the "not enough core"
error message. As I understand it, this cannot be solved at the user level,
but must be addressed at the system manager level. Either one needs to create
more swap space, or increase the user's quota if the machine uses process
quotas. I know that the latter is true on VMS systems, but I don't think it's
generally true under Unix. I don't know about Windows or MacOS.
Bill Thompson
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
