Windows Virtual Memory Management?

Windows Virtual Memory Management?

[Simtel20 Transfer]

Can someone say if/if not Windows virtual memory manager
does garbage collection?
If yes, do you need to tell it to so?  Like in the *.ini file(s)?
If yes, can one call a service to have it done right then?

If yes and it is controllable at runtime, do any/some/all of
the Ada runtimes utilize the Windows virtual memory garbage
collection?

Thanks in advance.
sam harbaugh HARBAUGH@ROO.FIT.EDU

Re: Windows Virtual Memory Management?

[R. William Beckwith]

Simtel20 Transfer (HARBAUGH@ROO.FIT.EDU) wrote:
: Can someone say if/if not Windows virtual memory manager
: does garbage collection?

No.

You must code the release of all of the resources your
program has used.  In fact, if you're programs does
not release these resources, some types of resources
will not get free'd even after your program terminates.

Specifically, watch out for graphics contexts.

Pretty much the opposite of virtual memory garbage
collection.

... Bill

-- 
e-mail: Bill.Beckwith@ois.com       |    Team Ada
Objective Interface Systems, Inc.   | dist, full O-O
1895 Preston White Drive, Suite 250 | multithreading
Reston, VA  22091-5448  U.S.A.      |    built in

Re: Windows Virtual Memory Management?

[Herndon Elliott]

        Microsoft came out with a simple but very effective tool in their
"Windows Resource Kit" called "sysmeter.exe".  Sysmeter is a simple icon
which tracks the user memory, graphical device interface memory and main
memory currently in use.  It displays this in three bar graphs.  If you have
ever wondered whats going awry in Windows, this little tool will explain it
and support what Mr. Beckwith stated in his post.  I can run WordPerfect,
for instance, and the GDI memory will drop down into the yellow.  When I
exit WordPerfect, the GDI memory will not return to the level prior to
running WP.  Other applications do this as well.  The worst case is when an
application crashes - the memory that it was using is lost to the system and
the only way I know to get it back is to restart Windows.

Windows 3.1 is a toy, but a very pervasive one.  Perhaps MS will fix some of
this stuff in Chicago, I mean Windows 94, er uh I mean Windows 95 or NT or
Windows for Workgroups or DOS 17.3 or...

Thanks,
Doc Elliott
LOSAT Computer Engineer
INTERNET:  helliott@losat.redstone.army.mil
205-842-8086
The opinions expressed herein are mine, and do not
constitute an official government position, unless
specifically stated as such.