[1.6.4][FTB Direwolf20 pack][SSP]TurtleOS crash?

I know the title says "TurtleOS crash?" but honestly I'm not sure what happened,

I was looking at a 150+ line program I made so I could fix it, I was scrolling down via down arrow and my computer (irl not cc computer) lagged and froze for a second, then all of a sudden I see my code is still there but the second to last line says "edit:157:Too long without yeilding" and the bottom line I see the cursor but it still says "Press ctrl to access menu" and typing over it makes it dissapear (I hate google spell check that says dissapear google says no) by the way, forgot to mention I did this on a mining turtle, weird thing is I'm wondering what happened because I wasn't running a program I was editting one.


EDIT: forgot to mention, I think the cause of this bug was entirely caused by my computer freezing, just a thought.

The word is correctly spelled "disappear". Does this consistently happen? It sounds like a one-off occurrence that happened to allow too much time to pass between the resume and the yield, triggering the yield protection code.

It's only happened once, and what's the yield protection code? I'm assuming it's what causes the "too long without yeilding" thing when a program is stuck on a loop doing almost literally nothing,

If a coroutine runs for ten seconds without yielding, it is aborted, killing the coroutine and yielding.

… which means that if your real computer stalls for ten seconds or more, ComputerCraft will think your script was running that whole time and terminate it.

The logic is that ComputerCraft can only run one script at a time, so if a script doesn't pause every now and then it can't switch to any others that players are trying to use. The "Edit" script, for example, yields most of the time - while it waits for you to type stuff in.

Bomb Bloke, on 08 January 2014 - 06:35 PM said:

… which means that if your real computer stalls for ten seconds or more, ComputerCraft will think your script was running that whole time and terminate it.

The logic is that ComputerCraft can only run one script at a time, so if a script doesn't pause every now and then it can't switch to any others that players are trying to use. The "Edit" script, for example, yields most of the time - while it waits for you to type stuff in.

I just can't help but laugh every time I look at that motto at the bottom of your posts,