No, I have watched the executive with 350 MB memory allocated and a
350 MB resident set when it is set to 256 MB limit. Of course, by
this time it is swapping like crazy on my 192 MB machine, but it
still happens on my 660 MB machine.
Marcus
I have noticed this as well, but I think what you are describing is
a little misleading. I've been watching my System monitor and here
is what I've determined.
If I set the memory of dx to 32 MB, then the executive never uses
more than 32 MB and doesn't swap to disk. For example if I set it to
32MB and then try and read a 75MB tiff, I assume that I should get
an out of memory error. However, I don't--I get more of a hung
process. It seems like the executive is requesting more memory but
is never given an error message back, instead it just keeps plugging
along processing, i.e. requesting memory and never getting any.
If I set the memory up to 256MB (I only have 128 MB installed), then
I get swapping invovled if I perform any manipulation on this 75MB
tiff. Sometimes, I then get to this out of memory type situation as
described above, but swapping is now involved and then I get a hung
swapping process.
So to clarify, the -memory option is still working correctly except
for when memory is completely used up. At that point instead of an
error being generated, a hung process (asking for memory) is created.
There have been changes and I will look to see if I can locate the problem.
David
This is on linux-ppc , (2000 release with updated lesstif and a few
other packages). I noticed it in particular on my laptop, which
has 192 MB of memory, so it is pretty easy to do things in dx which
cause massive swapping. It very quickly can consume 350MB or more
of memory, by which time swapping is so heavy that not much really
is happening any more. I have noticed this running many different
nets, none of which are particularly complicated (import, juggle a
little, RubberSheet and Image).
Marcus
Which platform? On my Linux station, the memory option is working just fine.
David
I just recently replaced my old dx-4.1.0 with a fresh compile of
the 4.1.1 cvs tree. I discovered that the memory limit arguments
to the executive are no longer honored, apparently. If I do
dx -edit -memory 256 blah.net
the executive is started with argument -M256 as it should be, but
then it proceeds to eat as much memory as it wants, rather than
stopping at 256 MB.
Has something been changed in the handling of memory allocation recently?
Thanks.
Marcus Mendenhall
--
.............................................................................
David L. Thompson The University of Montana
mailto:[EMAIL PROTECTED] Computer Science Department
http://www.cs.umt.edu/u/dthompsn Missoula, MT 59812
Work Phone : (406)257-8530
--
.............................................................................
David L. Thompson The University of Montana
mailto:[EMAIL PROTECTED] Computer Science Department
http://www.cs.umt.edu/u/dthompsn Missoula, MT 59812
Work Phone : (406)257-8530
