Memory Problems

[Pierre Sahores]

Ray Horsley a écrit :
> 
> Thank you xbury and Pierre,
> 
> I appreciate the suggestions, however, I've opened all 36 stacks I'm using
> for testing, set the Destroy Stack on Close and the Destroy Window on Close
> to true, and I also set the Always Buffer to false for all of them.  Sorry,
> no change.  I still find Metacard increasing in memory from about 17 megs to
> a little over 30 if I go to or refer to each of them.  Any other ideas?
> 
> Thanks,
> 
> Ray Horsley
> Developer, LinkIt! Software
> 
> on 2/20/03 6:18 AM, xbury.cs at clearstream.com at xbury.cs at clearstream.com
> wrote:
> 
> > The problem is with the caching of the stacks you open...
> > remove "always buffer",  and add "destroy stack on close" and "destroy widow
> > on close" from the stack properties window to free that memory up...
> >
> > -----Original Message-----
> > From: Ray Horsley [mailto:ray at linkitonline.com]
> > Sent: Thursday, February 20, 2003 16:53
> > To: metacard at lists.runrev.com
> > Subject: Memory Problems
> >
> >
> > Greetings,
> >
> > I'm having memory problems (but not personally).  I need to go to or refer
> > to several hundred stacks, but just one at a time.  I'm finding that even
> > doing so with just a list of 30 or so doubles the memory Metacard grabs.  It
> > stays doubled, slowing everything till I quit Metacard and relaunch.
> > Example:
> >
> > repeat with L=1 to number of lines of allStacks  -- list of 30 stack paths
> > put line L of allStacks into stackPath
> > set the defaultStack to stackPath     -- or go stack stack path
> > -- do some stuff like set scripts and save the stack
> > delete stack stackPath
> > end repeat
> >
> > Any ideas on how to keep memory usage down?  It would also be helpful for me
> > to be able to monitor memory usage if anyone knows how to do this from
> > within Metacard.
> >
> > Thanks!
> >
> >
> > Ray Horsley
> > Developer, LinkIt! Software
> >
> > _______________________________________________
> > metacard mailing list
> > metacard at lists.runrev.com
> > http://lists.runrev.com/mailman/listinfo/metacard
> >
> >
> > Visit us at http://www.clearstream.com
> >
> > IMPORTANT MESSAGE
> >
> > Internet communications are not secure and therefore Clearstream International
> > does not accept legal responsibility for the contents of this message.
> >
> > The information contained in this e-mail is confidential and may be legally
> > privileged. It is intended solely for the addressee. If you are not the
> > intended recipient, any disclosure, copying, distribution or any action taken
> > or omitted to be taken in reliance on it, is prohibited and may be unlawful.
> > Any views expressed in this e-mail are those of the individual sender, except
> > where the sender specifically states them to be the views of Clearstream
> > International or of any of its affiliates or subsidiaries.
> >
> > END OF DISCLAIMER
> > _______________________________________________
> > metacard mailing list
> > metacard at lists.runrev.com
> > http://lists.runrev.com/mailman/listinfo/metacard
> >
> 
> _______________________________________________
> metacard mailing list
> metacard at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/metacard

Ray,

Do you use global vars values in your code without resetting them to ""
betwin each stack load ? Else, just test your code, each line after an
other, to find where the memory is increased. I never had a memory
troubble that was not from my fact, along 6 years of mc programming.
Because Metacard is not Java, mc is probably not in fault, this time too
;-)

-- 
Cordialement, Pierre Sahores

Inspection académique de Seine-Saint-Denis.
Applications et bases de données WEB et VPN
Qualifier et produire l'avantage compétitif