Purge a stack from memory

Bob Sneidar bobsneidar at iotecdigital.com
Mon Jul 29 10:59:32 EDT 2019


Yes long standing issue ever since v9 I believe. Might have been since v7. I have to do the same thing. Apparently copies of things like library stacks (not the originals, but the COPIES created when building a standalone) are left open in memory. Not sure why they do that. Anything opened in the build process that was not open already should be closed, and everything already open before the process should be re-opened. 

Bob S


> On Jul 26, 2019, at 16:20 , doc hawk via use-livecode <use-livecode at lists.runrev.com> wrote:
> 
> On Jul 26, 2019, at 3:40 PM, Bob Sneidar via use-livecode <use-livecode at lists.runrev.com> wrote:
>> 
>> EEEEK!
> 
> Don’t be scared.
> 
> Be *very* scared . . .
> 
> There is something wonky about the whole  in and out of memory thing.
> 
> My  project is (during development) a bunch of   main s tacks,   with an mcp  to  rule  them all .  . .
> 
> Anyway, when I bump the version of one of them that has already been used,  something seems to stick around, so that I get an endless cycle of the two  stacks causing popups asking what to do with the other.
> 
> I’ve taking to quitting livecode after bumping and just plain reloading . . .



More information about the Use-livecode mailing list