Stacks not being removed from memory

[Jerry Daniels]

Swami,

I have had this problem in the past also and discovered ONE thing  
that might cause it.

If you refer to a stack (or any object) by its long name or long id,  
it will reload the stack to which it belongs into memory. This is  
because the long name or long id of any object also includes its file  
path. While this is extremely handy in many instances, it can also  
give you problems.

When i say "refer" above, I mean to say "using the long name or long  
id of an object in any expression."

Best,

Jerry Daniels

5 Reasons 12 Top Rev Developers Use to Constellation!
http://daniels-mara.com/products/5reasons.htm



On Dec 26, 2005, at 3:18 PM, Sivakatirswami wrote:

> OSX... 2.6...
>
> I still continue to get "stack already memory do you want to purge"  
> over and over again, but I have set all my stacks (and have  
> *always* set all my stacks") destroy both stack and window on close...
>
> Presumably this should clear them from RAM ? right?  but it  
> doesn't... from the IDE I must explicitely choose the "Close and  
> Remove from Memory" menu item in the IDE to be certain these stacks  
> do not have any latent versions in RAM. This is a nuisance where  
> one is closing some stack under script control.
>
> I was accusing Constellation of this problem before, but have  
> disabled Constellation and *still* get this purge request for  
> stacks which were closed, whose destroy stack is set to true.
>
> ?? Am I doing something wrong? Anyone else experience this?
>
>
> Sivakatirswami
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your  
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution
>