Ian,
This sounds like a possible culprit for the problem in our
application. Is there a way to find out what is causing this or to
verify it is occurring? Any code that can be written in? Any specific
places in the code to look for it?
Again, what we are experiencing is the program bogging down or simply
freezing up at various points throughout a day, but never at the same
place. This is in runtime mode only.... not in the development
environment. No programming bugs show up there.
Thanks.
Richard
On Sep 14, 2006, at 5:27 AM, Ian Wood wrote:
Memory leaks are where a program grabs memory when needed, but
doesn't release all of it afterwards. If the machine is up for a
long time, even a minor memory leak can tie up all available RAM,
bogging down the whole machine.
Ian
On 14 Sep 2006, at 10:23, Richard Miller wrote:
Peter,
Can you explain what you mean by a memory leak and how that
effects stability?
Thanks.
Richard
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
