Crash leads to RAM-hogging ruby process

[bitaxis]

An aspiring Ruby hacker decided to do something like this:

Turtle.draw do
  background maroon
 pencolor white
  9999999999999999999999999999999.times do
    forward 50
    turnright 90
  end
end

This caused a "glitch", at least on the iMac running OS X 10.7.2, where the current window dies, and a window is spawn. However, it left a ruby process running gobbling up all available memory, and slowing the machine to a crawl.

[deadprogram]

The "Run" button should change to a "Stop" button when you click on it. Clicking on it when a long running processing is going, should terminate it.

[hunterboerner]

Closing do to old age. Please retest on latest KidsRuby version and if problem persists, reopen the issue with details.