Bad Crash on Windows using LC8

Ralph DiMola rdimola at evergreeninfo.net
Mon May 23 17:42:12 CEST 2016


This "Save as" issue has been around for a long time(4/5/6/7/8). You can "Save as" and have no problem or suddenly the " already a stack in memory, please purge.." pops up or other times it happen immediately. And yes it always saves the stack correctly. I do version control by either "Save as" and then close LC and re-open or by coping the stack outside of LC and then do a standard issue "Save" (my preference).

This seem to be one of those hard to pin down things like the "Variable Shadows another..." issue.

I don't see a bug report for this.

Ralph DiMola
IT Director
Evergreen Information Services
rdimola at evergreeninfo.net


-----Original Message-----
From: use-livecode [mailto:use-livecode-bounces at lists.runrev.com] On Behalf Of Sannyasin Brahmanathaswami
Sent: Monday, May 23, 2016 11:09 AM
To: How LiveCode
Subject: Bad Crash on Windows using LC8

yesterday I was mentoring  a newbie with LC 8 stable on Windows.

Via Skype, he shared his screen. and we went throught the process of building a stack, making groups setting them as background, putting scripts into the stack scripts and calling from button etc.

He uses MSWord and PowerPoint and Excel most of his day… and has the habit of doing frequent backups by using "Save As" and adding/appending a version number-date in the file name and then keeps working in the new document.

He saved the stack then did a "Save As" and then "the pea soup hit the fan" as LC when into an infinite loop saying that there was already a stack in memory, please purge.. Cancel, Purge Save buttons in the dialog were all unresponsive and we were sitting there a bit aghast as LC keep looping and flashing through this, re-rendering/flashing the stack in the background and the dialog box on screen. Attempts to hit cancel did nothing. Control-dot interrupt did nothing…  He had to kill the process.

Fortunately the stack had been "Saved As" and so now he did have the document in it's last iteration + the one he had saved as… and neither were corrupt. But it was a scary moment… and not a very good experience for a new user of the software.

I am unable to replicate this on my mac.. though I have had a number of instances where if you choose "Close and Removed from Memory"  later in the session if you open that stack the IDE tells me that the stack is still in memory and do I want to purge it… this seems somehow related.

Anyone else getting this? has it been reported already?

BR

_______________________________________________
use-livecode mailing list
use-livecode at lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode




More information about the use-livecode mailing list