A stack "revCursors" is already in memory.

Paul Dupuis paul at researchware.com
Thu Jul 6 17:28:59 EDT 2023

On 7/6/2023 5:12 PM, J. Landman Gay via use-livecode wrote:
> On 7/6/23 9:26 AM, Paul Dupuis via use-livecode wrote:
>> I have a new Livecode 9.6.9  install on a new Windows 11 laptop. It 
>> was working normally for a while, and, now, whenever I launch it, I 
>> get a warning message:
>> A stack "revCursors" is already in memory. The Livecode UI does not 
>> ... etc..
>> Can someone advise what I need to do to address this? I seem to 
>> recall this problem has been seen before.
> I think it happens when you include cursors in a standalone build. 
> Sometimes LC adds it to your stack as well as to the executable. When 
> LC launches it see both the one in the stack and the one in the IDE.
> Check the substacks of your mainstack. If revCursors is in there, 
> delete it.

Thank you. that was the problem. I don't recall adding revCursors to my 
app's mainstack, but I did get a code execution error during a 
standaloneSaved handler before this started happening, so perhaps it 
left the build in a strange state. Fixed now. Thanks again.

More information about the use-livecode mailing list