At 12:00 PM -0400 6/3/01, Tab Julius wrote:
>What I meant was, it's certainly possible for people to create
>memory "leaks" just in Lingo. For instance, calling "play" to
>invoke a movie without "play done" will create the potential for a
>stack overrun, depending on your movie, and some other things. I
>don't know anything about the things you've written or how you've
>written them. It's entirely possible you're doing everything
>correct, or maybe not. Short of seeing the actual movies, I
>couldn't say.
>
>At any rate, try my suggestion of taking things out of the equation
>one by one and seeing if the problem goes away or not.
>
One easy culprit for a "leak" these days is the use of imaging lingo
on bitmap cast members. If you change a bitmap member, it won't get
unloaded because it has been modified. Do this enough and memory will
get fragmented and "leak"
/r
--
----------------------------------------
Roy Pardi [EMAIL PROTECTED]
----------------------------------------
[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/LUJ/lingo-l.cgi To post messages to the list,
email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED])
Lingo-L is for learning and helping with programming Lingo. Thanks!]
