Cancel infinite loop execution in jsfiddle

When you get an infinite loop in jsfiddle in Chrome, your only choice (that I know of) is to close the tab. Of course, this means you lose all your work in the current window! Is there an easy way to stop an infinitely executing script?

I have the developer tools open because I was doing some debugging.
I am able to pause the script and step through the loop.
I can't find anywhere to stop the script.
I can't modify the script or variables to stop the infinite loop (because the script execution occurs in an iframe on a separate domain, so modifying data in the iframe with JavaScript is not allowed and generates an Exception in the console).

It all started because I decided to swap directions on my loop from

for (var c = 0; c <= 11; c++)

for (var c = 12; c > 0; c++)

But as you can see above, I forgot to change it from c++ to c--.

Any ideas?? I still have the tab open and I'm hoping to get it back without closing the tab :-)

Solution 1:

How to do it without Developer Mode:

Open a new tab
Open the Task Manager with Shift-Escape
Kill task
Use back button for the killed tab (JSFiddle won't run the script)
Fix bug
Update

Or on MacOS,

Open Activity Monitor
Kill the first "Google Chrome Helper (Renderer)" process. It's probably JSFiddle
Fix the issue
Run the code

Solution 2:

With the developer mode, go into resources and find your script and copy and paste it into a text document or a new window. If you can't find it in resources, do a search for a variable or line of code you used.

Solution 3:

One way of breaking the infinite loop is to throw an unhandled exception, which will stop the execution of current call stack. To do so:

pause the debbuger
find a promising statement inside the loop, for example a function call: foo.bar(args)
in console, overwrite the function to throw : foo.bar=function(){throw 42;}
unpause the debugger

worked for me. I haven't tried, but I believe that by overloading getter or setter you can use the trick described above also for assignments and reads, not only for function calls. Also, by setting a variable to undefined, you may cause fatal error (and thus break the loop) if the field of this variable is used in the loop. For example delete foo.tab will break foo.tab[42] or foo.tab.bar. For some reason, simply writting foo=undefined in the console, will not do (perhaps it defines a variable local to the console window named foo).