My make-shift solution right now is to
- copy the url bar address
- close that tab
- open a new tab
- and then open the url in the new tab.
This is rather brute-force but its the only way I get Chrome to actually load a fresh copy of that page, instead of just continuing the existing running one. Emptying the cache has no affect because its not even trying to reload the page.
When I want to do this I close the debugger (letting the scripts finish running), then re-open it and hit refresh.
you could just deactivate all the breakpoints, reload the page, and reactivate them, its the last button (the fifth one starting from pause)
Google Chromes debugger is amazing, but it isn't like gdb where you can just start it or kill it, though you can enable/disable it by calling up the dev tools, think of it more like a monitor or manager for the interpreter, since JS for the most part is always running or running when JS needs to be parsed, the debugger simply interacts with the interpreter, thats how I've interpreted, if Im wrong I apologize.
If you want to actually stop all activity in the tab without actually closing it or the developer tools window, you can force it into the "Aw, snap!" state (with a handy reload button) via Chrome's Task Manager (More Tools -> Task Manager, select the tab, hit "End Process").
This way you can reload the tab immediately without waiting for all the scripts to finish. And the developer tools window will automatically reconnect when you hit refresh.
Google chrome debugger doesn't turn off, EVER. Once I created 1 breakpoint, but now there is no breakpoints but its still pauses and there is no breakpoint where it paused. I highly recommend not using the debugger at all, if you did, just uninstall chrome and reinstall and never set any breakpoints.