admin管理员组

文章数量:1133928

If the debugging window is open, the debugger starts hitting lines by itself even though there are no set breakpoints.

I have tried using the "Deactivate breakpoints" button and it doesn't make a difference if it is on or off.

This happens on any website.

If the debugging window is open, the debugger starts hitting lines by itself even though there are no set breakpoints.

I have tried using the "Deactivate breakpoints" button and it doesn't make a difference if it is on or off.

This happens on any website.

Share Improve this question edited Jul 13, 2020 at 23:11 Peter Mortensen 31.6k22 gold badges109 silver badges133 bronze badges asked Apr 5, 2013 at 10:34 Farhad-TaranFarhad-Taran 6,50217 gold badges69 silver badges129 bronze badges 4
  • 14 There's an option called 'Pause on exceptions' - Turn it off. – techfoobar Commented Apr 5, 2013 at 10:35
  • I never knew about this pause on exceptions thing! Can it also pause on anything that returns undefined? – Andrew Mao Commented Apr 7, 2013 at 0:44
  • 1 I have pause on exceptions disabled, and activate break points disabled, and chrome constantly switches into the debugger. I have no break points set either. – John Little Commented Nov 12, 2020 at 15:42
  • 1 @JohnLittle I'm having the same issue. Breakpoints are deactivated, it's not set to pause on exceptions, and I can't find any manual breakpoints. – jarrodwhitley Commented Mar 4, 2021 at 23:27
Add a comment  | 

14 Answers 14

Reset to default 172

You've accidentally set "Pause on Exceptions" to all/uncaught exceptions.

Go to the "Sources" tab. At the top right hand side, toggle the button that looks like the pause symbol surrounded by a hexagon (button on the far right) until the color of the circle turns black to turn it off.

There are a couple of reasons for this:

  1. You've toggled on the Pause On Caught Exceptions button. So, toggle it off.

  2. You've toggled a line (or more) to be paused on exception. So, toggle it off.

I have made it working...

Please follow the highlighted mark in the attached image.

If you were unfamiliar with the tools, it was likely that at some point while in the debugger you toggled a setting that was causing the debugger to stop the application.

I suggest you "Disable all break points":

Source:

https://javascript.info/debugging-chrome

  1. Open the dev tools. (Ctrl + Shift + I)
  2. Ctrl + Shift + P
  3. Search for "Do not pause on exceptions" and click it.

Press Ctrl+F8 to deactivate breakpoints. It worked for me.

You have multiple Google Chrome browser tabs open for the same URL and developer toolbar.

In some other tab, you have set breakpoints which are showing up when you are debugging in the current tab.

Solution: Close the developer toolbar in the other tab or the tab itself.

Blue dot still persists.

I only had one tab open and debugging off but the blue dot in the HTML Elements tab persisted.

I left clicked on the blue dot, dragged it down and away and it finally disappeared. I cleared browser cache and it finally fixed it.

i have this problem with special site so i just right click on javascript file has error that came to Watch and click add to ignore list and then just click continue and never come again

or

can deactive breakpoint then click on resume script executions - f8

For anyone that's searching why their chrome debugger is automatically jumping to sources tab on every page load, event though all of the breakpoints/pauses/etc have been disabled.

For me it was the "breakOnLoad": true line in VS Code launch.json config.

For me, this goofy behavior finally stopped when I unchecked the "Focus Sources panel when triggering a breakpoint" checkbox in Settings...Preferences:

This problem comes in any website. It is very easy to remove it. I have attached the image, follow that process, it will be done.enter image description here

Uncheck the "pause on caught exceptions" checkbox

Worked for me.

Go to Setting/Preferences scroll down to Debugger check disable JS and asynk stack traces as shown.

本文标签: javascriptHow can I stop Chrome from going into debug modeStack Overflow