🚀 go-pugleaf

While testing a large number of interacting programs (a daemon, clients and
servers), I am persistenly faced with unbounded swap file growth, even when
all other known resource utilizations are known to be constant.

Futhermore, the conditions inducing the growth require the interaction of
several programs, thus leaving me in the dark about which process is growing
the swap file.

Knowing that swap file size is related to process size(s), I wanted to
instrument the programs to measure their process sizes at chosen points to
narrow my search for the monumental memory leak.

Note that swap file size differentials around calls are not accurate, since
the swap file is affected globally, and a growth during a call to foo() could
be easily caused by another process (e.g.: let foo() be a remote procedure
stub).

Finally, I have stumbled across DosQueryMem(), but was not lucky enough to
figure out how it works if I wanted to measure heap space.  Some results
appear related to static space size, and to code size; however, experiments
with the heap were not very useful.

Please copy your reply to tonyk@ontos.com;

-- 
Antoun (Tony) Kanawati	| Ontos, Inc.		 | +----------------------+
tonyk@ontos.com		| Three Burlington Woods | |    SPACE FOR RENT    |
uunet!uupsi!ontos!tonyk	| Burlington, MA 01803	 | |                      |
tonyk@{corwin|flora}.ccs.northeastern.edu	 | +----------------------+