Repeat loops in and of themselves aren't culprits (what you do inside them 
might be).

A little more information is needed:

1) Is this Mac or Windows?  Macs (pre-OS/X) are notorious for horrible 
memory management.

2) Is this 4% a permanent loss, or just while it's running?  If you exit 
the program, is the 4% reclaimed?  If so, then it's not a leak, just what 
it needs to operate.

3) Do you get an additional 4% loss every time you run the program?  That 
is, it keeps dropping by 4%, until you eventually have no memory?  Because 
that's much more in keeping with what a true "leak" is.

4) What third-party Xtras are you using?

5) Are you using any Xtras that you're instantiating but not closing when 
you're done?

- Tab

At 09:29 AM 2/18/02 -0500, Carol Mahaffy wrote:
>hey list --
>i have a cd that was created about 2 months ago that i need to help the
>performance. The problem is that after you continously play the cd it sucks
>up your system memory. (about 4%) Could anyone give me an idea of how to go
>about looking for this? I was thinking that repeat loops might be the
>culprit but after extensive removal it is still happening. I just don't know
>of  a good way to logically disasemble this to see where the error is.
>thanks
>-- carol

[To remove yourself from this list, or to change to digest mode, go to 
http://www.penworks.com/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!]

Reply via email to