What I had suggested (closing the form, returning to the program and
opening up the form again) was sort of test #1. Wanted to find out if closing
the
form in itself would be enough to release memory. So from what you said,
this didn't help? Memory still not being released?
Out of options for you, sorry. Probably a year I started a thread asking
if there was a way to release memory like we used to be able to do in the DOS
environment, because of frequent temp table corruption problems I was
having at various clients. I just now looked up a program we used to run at
most
of our DOS clients to trap memory usage. But I doubt the "zip
nothing.exe" works anymore.
But just for giggles, here's the program:
SET V vdosfree = (ISTAT('memory'))
IF vdosfree < 1000 THEN
DISCONNECT
ZIP nothing.exe
SET V vdosfree = (ISTAT('memory'))
IF verror <> 0 OR vdosfree < 135500 THEN
wri 'Refreshing memory...'
ZIP ret nothing.exe
ENDIF
CON andriana
ZIP nothing.exe
DEBUG vdosfree = (ISTAT('memory'))
DEBUG WRITE 'Memory now at', .vdosfree
DEBUG PAUSE 1
ENDIF
return
Karen
> Dennis you are right with my first test.
>
> Originally I would just refresh the web content... Memory usage increased
>
> Then I tried a closewindow, start new form... Had that in a wrong spot,
> and opened more and more forms. (my bad) Memory usage increased
>
> Now the start eep that calls the form originally is set up like you are
> suggesting... completely closing the form on each iteration of the loop.
> Memory usage increases.
>
> I am guessing the ONLY way to get the memory to reset is to close R:Base.
> If that isn't the case, that would be best for me as I don't know how to
> open an instance of R:base to a particular monitor.
>
> Without fixing this, This application uses up memory so fast that twice a
> day things fail. Have to manually start and stop it. Not good for an
> automated process.
