| Re: IDL memory allocation limitation [message #20431] |
Fri, 23 June 2000 00:00 |
promashkin
Messages: 169
Registered: December 1999
|
Senior Member |
|
|
Mark Rivers wrote:
> ....I would stop those programs right after
> booting, and they were no longer running.
.....
> ... but if they
> never started then the problem went away ...
This seems more like an OS overlook - not to recover all memory after
software quit. IDL uses what it sees, it is not a memory manager. Or is it?
Cheers,
Pavel
|
|
|
|
| Re: IDL memory allocation limitation [message #20432 is a reply to message #20431] |
Fri, 23 June 2000 00:00  |
Mark Rivers
Messages: 49
Registered: February 2000
|
Member |
|
|
Mark Rivers <rivers@cars3.uchicago.edu> wrote in message
news:H9r45.99$v3.1429@uchinews...
>
> I am having a problem with memory limitations in IDL on Windows NT which I
do
> not understand, and wonder if someone could help with. I have 2 Windows
NT
> systems, "ferrari" and "lotus". These systems are configured as follows:
I found the problem. There were a couple of programs which automatically
started when one logged in to this machine, including IomegaWare, which is
software to access a Jazz drive. I would stop those programs right after
booting, and they were no longer running.
However, when I removed the programs from the Startup folder, so that they
never started then the problem went away and I could get the entire 1 GB of
memory which I should. This is a very strange problem, since other
applications should never interfere with IDLs ability to get the 1 GB of
memory as long as the page file has room, which it did.
Mark Rivers
|
|
|
|
| Re: IDL memory allocation limitation [message #20435 is a reply to message #20431] |
Fri, 23 June 2000 00:00 |
Mark Rivers
Messages: 49
Registered: February 2000
|
Member |
|
|
Julie Greenwood <julieg@NOSPAMoceanweather.com> wrote in message
news:sl78m3t2e7f61@corp.supernews.com...
> Check that your virtual memory settings are sufficient - they are limited
> only by free disk space (Start | Control Panel | System)
Both systems have 2GB fixed size paging files. When IDL reports that there
is not enough memory to create a (1024, 1024, 756) byte array there is still
953 MB of free RAM and 3 GB of free virtual memory, as reported by Task
Manager/Performance.
Mark Rivers
|
|
|
|
| Re: IDL memory allocation limitation [message #20436 is a reply to message #20431] |
Fri, 23 June 2000 00:00 |
Julie Greenwood
Messages: 6
Registered: December 1999
|
Junior Member |
|
|
"Mark Rivers" <rivers@cars3.uchicago.edu> wrote in message
news:H9r45.99$v3.1429@uchinews...
> <snip>
> My problem is in the amount of memory which IDL can allocate. The
following
> table shows the maximum size BYTE array which I can allocate in IDL. This
is
> right after a system reboot, no other applications are running and this is
the
> first command entered in IDL.
>
> ferrari lotus
> b = bytarr(1024, 1024, 1007) b = bytarr(1024, 1024, 755)
>
> Thus, on ferrari I can allocate essentially 1 GB of memory, which is the
limit
> for a single Windows NT process. However, on lotus I can only allocate
.75 GB.
> Can anyone suggest why lotus would be limiting that maximum size array I
can
> allocate? It is a serious problem for the applications I am running.
Check that your virtual memory settings are sufficient - they are limited
only by free disk space (Start | Control Panel | System)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Juliet G. Greenwood
Senior Programmer
Oceanweather Inc.
JulieG@Oceanweather.com
http://www.oceanweather.com/
http://www.thehungersite.com/
The Hunger Site - Donate Food for Free to
Feed Hungry People in the World.
The Site's Sponsors Make the Donations.
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
