Paused in debugger in chrome?

T

21

191

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?

Trigraph answered 11/10, 2012 at 6:31 Comment(2)

+1 You might also find this useful: How-to-terminate-script-execution-when-debugging-in-Google-Chrome – Twit 1/4, 2015 at 14:21

Try slowing the internet speed by throttling to "Slow 3G", by the time it clears the network tab, you can easily right click and copy the request you want as curl. Simple & gets my job done without any extension or anything. Hope it helps. – Ima 22/11, 2022 at 18:45

M

263

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.

Macruran answered 15/10, 2012 at 14:14 Comment(8)

sometimes you should know where to click. – Lesleylesli 5/11, 2012 at 16:44

@Macruran I added a screenshot of the icon, hope you don't mind. – Duramen 23/3, 2013 at 6:19

Thank you so much. It was beginning to frustrate me. I don't even remember clicking that button. – Radiophone 29/5, 2013 at 15:29

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. – Harlie 23/8, 2016 at 8:30

@Harlie 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. – Yong 29/12, 2017 at 21:22

wow thanks @Macruran I was wondering why I had to do this for every site for a couple of days now >< – Annabal 14/11, 2018 at 21:13

it might be in the Top Right – Rhinehart 13/3, 2021 at 16:8

I've discovered that some web pages contain JS which trigger the pause if the developer console is open. Frustrating! Apparently it's used to stop people being able to easily poke about with the scripts. – Computer 12/10, 2023 at 16:25

S

113

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.

Any XHR Flag in Chrome Dev Tools

Uncheck it for Chrome to work normally again.

Sapphera answered 18/10, 2012 at 9:29 Comment(0)

K

60

This can also cause the issue

Break Point icon at top right should be blue like this

enter image description here

Should not grey like this

enter image description here

Kancler answered 10/2, 2015 at 18:30 Comment(3)

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. – Sapphera 20/11, 2017 at 10:13

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. – Demarcation 7/5, 2022 at 11:41

@Sapphera I have no idea what is causing this for me but using this answer helped. I don't have Any XHR enabled. – Mammy 29/10, 2022 at 8:6

H

14

If you navigate to Sources you can see the pause enter image description here 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 enter image description here .

Hidden answered 28/10, 2013 at 9:10 Comment(1)

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.") – Underthecounter 31/1, 2017 at 13:18

T

13

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

This is the short solution.

Treytri answered 31/1, 2019 at 15:19 Comment(0)

G

12

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

Gelya answered 27/5, 2014 at 9:9 Comment(0)

M

10

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

Mutazilite answered 19/1, 2016 at 14:50 Comment(0)

G

8

enter image description here

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.

Guyon answered 30/8, 2013 at 4:15 Comment(0)

A

8

Click on the Settings icon and then click on the Restore defaults and reload button. This worked for me whereas the accepted answer didn't.

Astigmatism answered 7/10, 2015 at 18:36 Comment(1)

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. – Defenestration 4/2, 2016 at 23:22

F

4

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!!

Fuzz answered 1/10, 2017 at 7:24 Comment(0)

M

3

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

Machos answered 19/11, 2015 at 16:6 Comment(0)

Z

2

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.

Zeller answered 5/9, 2014 at 4:0 Comment(0)

E

1

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

Eskridge answered 5/3, 2021 at 14:31 Comment(1)

Same for me, it was a random chrome extension. This should be upvoted higher. Huge headache to figure this out. – Leopoldeen 1/7, 2022 at 16:27

T

1

I solved it like this:

✅ Just make sure you have unchecked both of these:

Therewithal answered 25/8, 2023 at 17:13 Comment(0)

P

0

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

Pika answered 21/1, 2015 at 12:43 Comment(0)

O

0

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.

Obbard answered 9/1, 2020 at 14:59 Comment(0)

R

0

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.

Rhamnaceous answered 1/5, 2020 at 2:20 Comment(0)

W

0

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

Wimmer answered 2/7, 2021 at 12:7 Comment(0)

M

0

The Chrome Debugger Pause Button -- international hide & seek champion!

Here is what it looks like in 2022:

Myocarditis answered 12/10, 2022 at 17:0 Comment(0)

C

0

In my case I was enabled Pasue on Caught Exceptions

Cliffhanger answered 4/10, 2023 at 18:6 Comment(0)

M

-1

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

Montcalm answered 23/7, 2019 at 10:9 Comment(0)

Recommended topics

Hot tags