When debugging in chrome, the scripts are always paused in the debugger even if there are no break points set, and if the the pause is un-paused, it again pauses itself.
There was a syntax error in my for
loop. This caused the pause error.
In my case, I had the Any XHR
flag set true on the XHR Breakpoints
settings, accessible over the Sources tab within Chrome's dev tools.
Uncheck it for Chrome to work normally again.
You can just go to Breakpoints in the chrome developer console, right click and remove breakpoints. Simple.
This was happening to me. I had a breakpoint on subtree modifications on the body tag, and every time I removed the breakpoints, they would be back after I refreshed. I was so confused, and I even removed all DOM breakpoints, but the phantom body subtree modification breakpoint kept coming back. Eventually, I reloaded the cache, and they disappeared.
If you navigate to Sources you can see the pause button at the bottom of the DevTools. Basically there are 3 possible pause option in DevTools while debugging js file,
Don't pause on exceptions() :
The pause button will be in grey colour as if "Don't pause on exceptions" is active.
Pause on all exceptions() :
The pause button will be in blue colour as if "Pause on all exceptions" is active.
Pause on uncaught exceptions() :
The pause button will be in purple colour as if "Pause on uncaught exceptions" is active.
In your case, if you don't want to pause, select Don't pause on exceptions. To select, toggle the pause button till it become grey.
Really silly issue that I ran into that led me here with the debugger; command.: "debugger;" has a watch set on it.
It caused a page that just said debugger; to appear between every page load.
The way to disable it is to just right-click said Watch and click "Delete watch expression".