On Thursday, 95/11/30, mark lewis wrote to David Noon about "The
Handle Messiah" as follows:

ml> DN> Is there any REXX involved? A lot of REXX execs open files and then
ml> DN> don't close them with a call to STREAM(...,'C','CLOSE').
ml> 
ml> do you think this might have anything to do with a memory leak i'm
ml> having with OS/2 v2.11 ?? i've a REXX script that runs in the
ml> background. when it detects a semaphore file on a RAM drive, it
                                                      ^^^^^^^^^
Hi Mark,

Are you cleaning up the RAM drive? This could be your memory leak.

ml> starts up a DOS .BAT file... the majority of the processing in this
ml> .BAT file is DOS stuff except for about 4 things. these 4 things are
ml> OS/2 native programs which i run from .CMD files via HSTART and use
ml> HWAIT to delay until they are complete... my problem is that after a

Since these are separate processes (address spaces) they should be
cleaned up by OS/2's recovery and termination manager, freeing up any
resources they might have allocated during their execution.

ml> fresh boot, i've about 8Meg of RAM that is unused... after each run
ml> thru this processing, i loose memory... after about a day and a half
ml> i have to reboot to clean out the swap file and regain my memory and
ml> speed...

Do you mean 8MB of _real_ storage or just virtual storage within the
address space? If real storage then you are losing memory to fixed
(i.e. non-swappable) pages becoming committed, which would also tend to
incriminate the RAM drive. The REXX stuff is nearly all swappable.

As an experiment, try using spinning DASD instead of a RAM drive.

Regards

Dave


 * KWQ/2 1.2i * Hey Bill, I've upped my standards to OS/2.  Now UP YOURS!

--- Maximus/2 3.00