At 15:34 +0530 07/01/03, [EMAIL PROTECTED] wrote:
Does "grinding halt" mean something sudden like a crash, or is it rather that performance at one point gradually becomes slower and slower?the whole thing comes to a grinding halt after a few minutes.
If the later then that could be an indication of a gradually accumulating memory management problem.
Maybe you're somehow generating a large number of image-objects, that are not disposed of. One possible explanation is an OOP hierarchy with a flaw in the destruction scheme. An example of one such possible flaw is timeoutObjects that doesn't release their targetObjects, because of a bug, if you don't initialize them into a variable.
Or maybe you're allocating memory in such a way that the memory-space quickly becomes fragmented.
When your memory space is consumed to the point where there is no more available RAM, virtual memory on the harddisk will typically be used, and that could seem like a "grinding halt".
Anyway, if you think that memory could be the issue, and you haven't explored that yet, you should look into things like the memory-inspector, and lingo such as the freeBytes and the freeBlock.
Actually I'm not quite sure if those lingo commands are adequate on systems where Director doesn't have any insight into the underlying virtual memory mechanism of the OS.
Maybe you need memory inspection tools external to Director to gauge the memory consumption.
On OS X you could use "Process Viewer" or "top" in the "Terminal".
I'm sure there are similar tools on Recent versions of Windows.
Maybe someone else could answer the more general topic here of memory gauging with Director.
Which tools and strategies do you use to monitor memory consumption?
Jakob.
[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!]
