
this may however skip one breakpoint, but may work if you're in a loop.) (Of course this doesn't help if you are trying to step through functions, though perhaps you could dynamically add in a throw 1 or z() or somesuch in the Sources panel, ctrl-S to save, and then ctrl-R to refresh. Or maybe call a non-existent function: debugger z() Assuming you're in break-on-error mode (the pause-icon toggle), you can ensure a break happens by instead doing something like: debugger throw 1 then I think the page will continue running forever until the js runtime yields, or the next break. If you are encountering this while using the debugger statement, debugger Refer to James Gentes's answer for details. Juacala's workaround is still useful when debugging in IE or Firefox.Ĭhrome Dev Tools at last added a proper way to stop script execution which is nice (although a bit hidden). I even went as far as to test it in Chrome v22 and found that this was working this way even at that time. Google Chrome has its own Task Manager which can kill a tab process without closing the tab itself, keeping all the breakpoints and other stuff intact. I have tested it in all above browsers and can confirm it is working.įinally, after over 2 years and almost 10K views, the right answer was given by Alexander K. For example, if you are using jQuery, running delete $ from console will stop execution once any jQuery method is encountered.

When pressing F5 (Refresh) while a script is paused:
#JS ACTIVE TIMER DEBUGGING CODE#
Pressing "Reload this page" runs the rest of the code and even submits forms as if pressing F8 "Continue". When stepping through JavaScript code in Google Chrome debugger, how do I terminate script execution if I do not want to continue? The only way I found is closing the browser window.
