Re: Forms 4.5 : call_form deallocation problem
Date: Fri, 09 Oct 1998 16:14:16 GMT
Message-ID: <6vlcoo$mlg$1_at_nnrp1.dejanews.com>
That is what call_form is supposed to do, It never de-allocates the memory until you quit the application. Though OPEN_FORM has some restriction you might wanna try that out.
In article <3609475f.769648866_at_news.leading.net>,
joebrown wrote:
> I suspect you're on a Unix platform...
>
> In the Windows Environment, I've watched memory consumption by forms.
> Runform does not want to let go, once it's allocated memory.
>
> I have observed after exit and calling the secondary (child) form
> again no additional memory is allocateed.
>
> I've used Open_form successfully, replacing the second form with
> another form, and have not observed any furhter memory consumption.
>
> I hope this holds true for the Unix world.
>
> "Patrick Martel" <patrick_martel_at_suez-lyonnaise-eaux.fr> wrote:
>
> > We migrated an application from Forms 3.0 to Forms 4.5 and we meet big
> > problem related to call_form memory allocation (no deallocation in fact).
> >
> > Only solution we know is to close session.
> >
> > Exist a fix or work arround solution ?
> >
> > Thanks
>
> --
> joebrown
> _at_leading.net
>
-----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own Received on Fri Oct 09 1998 - 18:14:16 CEST