ChatGPT解决这个技术问题 Extra ChatGPT

Paused in debugger in chrome?

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.

What can be done?


M
MendelG

One possible cause, it that you've enabled the "pause on exceptions" (the little stop-sign shaped icon with the pause (||) symbol within in the lower left of the window). Try clicking that back to the off/grey state (not red nor blue states) and reload the page.

https://i.stack.imgur.com/QltAW.png


sometimes you should know where to click.
@DavidJ I added a screenshot of the icon, hope you don't mind.
Thank you so much. It was beginning to frustrate me. I don't even remember clicking that button.
Pausing on exceptions is neither a problem (@Luja) nor an issue (@Bosworth99) or something to be frustrated about (@dminer). It is a very helpful feature in debugging. It only takes a couple of hours (or less depending on your experience) to view all the options in the devTools UI and get comfortable with them. Please invest this time! It will help you immensely in your day-to-day debugging routine.
@CodeVortex Just because something is useful, that doesn't stop it being problematic if it is doing something you don't want right now and you don't know how to stop it.
k
k0pernikus

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.

https://i.stack.imgur.com/ognjb.png

Uncheck it for Chrome to work normally again.


That was the same issue I was having
Same issue here too, thanks - this was driving me nuts.
you just saved my life :-)
@Alex Aw, cute :D
I had it on Animation - drove me nuts until I read this, thanks!
W
Wolfie

This can also cause the issue

Break Point icon at top right should be blue like this

https://i.stack.imgur.com/grfnQ.jpg

Should not grey like this

https://i.stack.imgur.com/TrB5g.jpg


This is misleading as it disables stopping at any breakpoints, not the one at pageload. So this prevents also the breakpoints you want. The actual issue is not the button at the top right, but the checked "Any XHR" box at the bottom left.
This is good when you need to access the Debug window while being able to select something on the page, but the page gets locked by the script.
Ahhhhh! Finally!
C
Community

https://i.stack.imgur.com/DlSc7.png

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.

https://i.stack.imgur.com/DlSc7.png


Thanks for the screenshot!
THANK YOU! You're the only one who answered this with a CLEAR indication of which is which. Tooltips should be helpful, not confusing: when it's grey, and thus disabled, the tooltip says "Pause on Exceptions"... which tooltips for toggles were less idiotic ("Don't pause on exceptions. Click to toggle.")
r
rayking

And there is some options below ,if you have checked some,when the condition is active,the breakpoint debugger also active

https://i.stack.imgur.com/VnNfu.jpg


G
GabrieleMartini

You can press CTLR+F8 to activate or deactivate breackpoints.

This is the short solution.


o
ouonomos

https://i.stack.imgur.com/8oniU.png

Yep. I'm just learning chrome dev tools today, and found the same thing -- if the above fails, expand the area pictured here and look for breakpoints you may have set and forgotten.


c
codeymcgoo

https://i.stack.imgur.com/QQNQv.png


I had the same experience, and felt like I was taking crazy pills: cl.ly/f4Jj The "restore defaults" in settings fixed this for me. No idea what it was, but as it wasn't happening in Canary I knew it was something specific to Chrome's dev tools.
S
Shailendra Singh Rajawat

At the right upper corner second last icon (encircled red in attached image) is for activate/deactivate debugging. Click it to toggle debugging anytime.

Chrome Debug console


S
Saif

Its really a bad experience. if the above answer didn't work for you try this.

Click on the Settings icon and then click on the Restore defaults and reload button.

Press 'F8' until its became normal.

Happy coding!!


P
PW Kad

Another user mentioned this in slight detail but I missed it until I came back here about 3 times over 2 days -

There is a section titled EventListener breakpoints that contains a list of other breakpoints that can be set. It happens that I accidentally enabled one of them on DOM Mutation that was letting me know whenever anything to the DOM was overridden. Unfortunately this led to me disabling a bunch of plug-ins and add-ons before I realized it was just my machine. Hope this helps someone else.


A
AllisOne

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".


v
vikrant

For me this was due to a chrome extension, i turned off a few unwanted extensions and the message was gone.


Same for me, it was a random chrome extension. This should be upvoted higher. Huge headache to figure this out.
Z
ZubairAnwar

You can just go to Breakpoints in the chrome developer console, right click and remove breakpoints. Simple.


R
Ramona Liliana

Threads > switch "Main" to "app"

In the "Threads" section I changed the context from "Main" > to "app". The "app" should have a blue arrow aside.


c
codecubed

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.


A
Anirudh

There was a syntax error in my for loop. This caused the pause error.


d
dan1st

https://i.stack.imgur.com/FFecl.jpg

no need to worried. just click here and refresh your page.