I have been experiencing similar problems. During execution, a stack will sometimes become completely unresponsive, and not just the stack, but the whole Mac OS. This occurs on both an MacBook Air and an iMac under the latest OS X (but also occurred under previous OS X versions) and under LiveCode 8.1.3*, LiveCode 8.1.1*, LiveCode 8.0.2 and LiveCode 7.1.4 and probably under some earlier versions, too).
The only solution is to shut down the machine in use with the power switch, as Force Quit cannot be summoned: the Finder is simply unresponsive, the Dock fails to appear, there is no response at all.
After some testing, I believe there is a connection with the use of sounds in the stack. I have modified the stack to run without the sound elements (one or no sound-clip included on each card); the limited OpenCard script has been eliminated; there is no CloseCard script; the simple script used in the test is no more than a go to next cd for all cards. While the LiveCode script was running, the Activity Monitor was active.
- with the sound-clip eliminated from all cards, the same simple script shows a Threads count starting at 5 and ending at 7;
- with the sound-clip included, the Activity Monitorshows an ever-increasing number of Threads, with the Threads count in this case starts at 10 and ends at 894.
LiveCode was started afresh for each test.
I have posted videos of this at http://davidneale.eu/livecode/threads-i ... sound.html
The tests were performed with LiveCode 8.0.2.
*Re LiveCode 8.1.1 and 8.1.3, it is not even possible to run the simple script under 8.1.1 and 8.1.3 with the "sounded" stack: everything halts after some 500 (it varies from test to test with the same data) Threads are reached, when a card stops for several seconds, then goes to the next one, then the Activity Monitor shows "LiveCode not responding (in red). With the "soundless" stack, everything works fine (at least as far as this test is concerned), with Threads starting at 5 and ending at 7.