AnsweredAssumed Answered

VRf: Release memory of ActiveX Objects

Question asked by VRFuser on Mar 25, 1999
Latest reply on Mar 25, 1999 by VRFuser
From:                David Paslay <DPASLAY@coinco.com>
To:                  Georg Nied <gn-software@gmx.de>
Copies to:           VRf mailing list <hpvxd_xc@hpislsup.lvld.hp.com>
Subject:             VRf: Release memory of ActiveX Objects
Date sent:           Thu, 25 Mar 1999 13:02:02 -0600

[...]
> See this e-mail from when I brought this up on the reflector
> long ago.
[...]

> > > I think I better mention at this point that there is a known bug in VEE
> > > 5.0 (that will not be fixed in 5.01) where VEE won't release object
> > > references.  In principle an AxA
> > > app should go away after the final reference
> > > is released, but that never happens with VEE unless (I think) you exit
> > > VEE.
> > >
> > > This is an inconvenience but redesigning VEE to deal with it is proving
> > > tricky.
>
> The only way the references get released is if you load a new program or
> exit VEE ... I just received that clarification.
>
> [<>] gvg
> --
>     Greg Goebel                           
>     Hewlett-Packard / MXD Marketing
>     pctm@lvld.hp.com
>     http://www.geocities.com/CapeCanaveral/Launchpad/6000

What is the result of that bug?
What resources and which ammount of memory will not be released?
Is it under these conditions possible, to write a VEE-application
containing activeX-automation with dynamically SET-ing and
CLOSE-ing Objects that should run 24 hours a day?

    
Georg Nied
Software Development
51149 Koeln
Germany
gn-software@gmx.de
ICQ 23490440

Outcomes