Your definition of a memory leak is way, and I mean WAY
off! I'm an electrical engineer, and I know a thing or
two about programming.
First off, a true memory leak has nothing to due with the
amount of memory a program uses! A memory leak occurs
when a program has finished using a certain portion of
the memory that has been allocated to complete a task and
the program DOES NOT release that portion, causing more
and more memory to be used up, until the program
crashes. Just because the virtual memory takes a huge
hit, DOES NOT imply there is a memory leak. If that were
so, then every program on systems without enough memory
to run all the programs together would ALL have memory
leaks. Yet on another system with substantially more
RAM, the "memory leak" would be non-existant. If you are
running at about, or even below, the minimum memory
requirements for all the programs running on the system,
then when MSAS hits the registry, then it's likely to
need more RAM, as the registry can be HUGE on some
systems.
For a TRUE definition of a memory leak, go to google.com
and type in memory leak? into the text box and click on
the I'm Felling Lucky button.
Please get the facts strainght before making a statement
about the performance of a program, PLEASE! Programmers
in general hate it when people tell them, or go and tell
others there's a problem and there isn't!
Slightly peeved programmer,
Alan
PS Don't send email to the above address if you are going
to be hateful and spiteful in the email, as I WILL put
your email address in my ISP's blocked sender list, and I
won't have to read your completely unappropriate emails!
Just thought I'd let you know that.
