Some kind of memory/purge error

[Robert Brenstein]

>I'm encountering several problems with proper purging of stacks. Here's the
>simplest example:
>
>I have several stacks open (some are substacks).
>I close one stack (which has the destroystack and destroywindow commands in
>it)
>I check the revloadedstacks function and the Application Overview...both
>show the stack as being purged. No sign of it.
>I go to open a different stack which has the SAME stack name (but a
>different file name).
>I immediately get a dialog box asking what I want to do with the previous
>stack (i.e. which has the same stack name).
>
>This appears to be some kind of bug in the program. It is causing an
>inability to properly purge stacks from memory, as I'm continually opening
>and closing numerous stacks but some are not being fully purged. Obviously,
>it doesn't take long before I've got a serious memory problem.
>
>Is there a workaround for this, and has anyone else encountered it? Is this
>a known bug?
>
>Thanks.
>Richard Miller
>

Since you mention having substacks, check whether the problem is 
related to using them. I just discovered that destroystack and 
destroywindow properties apply only to mainstacks. Closing substacks 
does not completely remove them from memory (for example, 'there is a 
window' continues to return true -- one needs to use 'the mode' to 
check whether a substack is open or not). I also seem to see some 
side-effects if the mainstack is closed but its substacks remain open 
but haven't pinpointed anything specific. All this is a result of 
having substacks. Requiring unique names of mainstacks is a separate 
story.

Robert