We had a similar issue in D7 and eventually after much pressure MACR
supposedly privately stated that freebytes was reporting inaccurate results
(however, realize that that is a 3rd or 4th party removed statement, in
otherwords don't hold me responsible for its accuracy). I wouldn't know
whether or not the issue was or wasn't resolved in D8 and have no idea
whether the statement in question is accurate. I noted it here because it
may explain why you are seeing different results between the task manager
and the freebytes. It could also indicate that Director is freeing memory
internally to reuse but not necessarily releasing that block of memory back
to the OS directly... in otherwords Director might be retaining memory to
reallocate to the next image without giving it back to the OS in the
imbetween time.. not sure if it could work that way but might be another
possiblility to consider.
Sincerely
Mark R. Jonkman
> -----Original Message-----
> From: Colin Holgate [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, June 03, 2001 12:57 PM
> To: [EMAIL PROTECTED]
> Subject: Re: <lingo-l> FreeBytes LIES - Memory leak in Director 8
>
>
> >So Freebytes is NOT reporting correctly. So now I will start stepping
> >through the program watching the Task Manager for potential problems.
>
> How do you know for sure that the task manager isn't making the mistake?
>
>
> [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!]
[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!]
