Remote Debugger Anomalies

[Sannyasin Brahmanathaswami]

On 9/13/18 10:47 AM, Monte Goulding via use-livecode wrote:
> OK that definitely gives me an idea. The cache is meant to be cleaned up when the socket closes so should be happening between launches of the app but we can also force the debug session to end during the deploy of the new version which will hopefully ensure things are cleaned up.

OK, given that we understand the problem, to be solved one day.

Until then, how do we work around it?

Give an error, and the Script Editor "becomes"

stack "d2dc63f5-efeb-412c-a6ae-741d60b569de"
card id 1002

What is best practice to get out....and back to the original stack/scripts?

BR