At 18:40 +1200 19/09/01, Sean Wilson wrote:
> > An object referenced by a timeout only seems to get destroyed
>> properly when
>> the timeout's target is voided, but not when the timeout is just simply
>> forgotten.
>
>Hi Luke,
>
>Yes, this is what we have both noticed too. Do you consider this rates as a
>"heads-up" or do I hear "bug"? Did you notify MM so that, at least, a
>technote can be generated?
>
>I also did a quick test examining the freeBytes, and the value displayed
>definately dropped on a continuous basis when creating a timeout referenced
>object and having it auto-destruct during a frame-related event. But I was a
>bit leery of reading too much into it as when the freeBytes approached the
>freeBlock within such-and-such an amount, I'd suddenly see the freeBytes
>jump up again.
Which makes me think:
Is the target *never* garbage collected, or is the garbage collection
process of timeOutTargets for some reason deferred more than usual?
Jakob
[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!]
