debugginggoogle-chromegoogle-chrome-devtools

Reputation: 2877

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?

Upvotes: 197

Answers (22)

Alexander Phung

Reputation: 105

In my case, I have some breakpoints in DOM Breakpoints, you need to remove them to void enter debug mode, you can see below image

Upvotes: 0

ThanHtutZaw

Reputation: 107

In my case I was enabled Pasue on Caught Exceptions

Upvotes: 0

mahdi

Reputation: 493

I solved it like this:

✅ Just make sure you have unchecked both of these:

Upvotes: 1

Shailendra Singh Rajawat

Reputation: 8242

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

Upvotes: 11

HoldOffHunger

Reputation: 20948

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

Here is what it looks like in 2022:

Upvotes: 0

Nishant Butani

Reputation: 31

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

Upvotes: 0

DavidJ

Reputation: 4577

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.

Upvotes: 267

vikrant

Reputation: 2287

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

Upvotes: 1

codecubed

Reputation: 780

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.

Upvotes: 0

Ramona Liliana

Reputation: 5

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.

Upvotes: 0

Anirudh

Reputation: 3428

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

Upvotes: -1

Nasser Albelbeisi

Reputation: 567

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

This is the short solution.

Upvotes: 13

k0pernikus

Reputation: 66817

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.

Upvotes: 115

Siful I

Reputation: 1932

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

Upvotes: 4

Asif Asghar

Reputation: 906

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

Upvotes: 62

AllisOne

Reputation: 31

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

Upvotes: 3

codeymcgoo

Reputation: 593

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.

Upvotes: 8

ZubairAnwar

Reputation: 83

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

Upvotes: 0

PW Kad

Reputation: 14995

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.

Upvotes: 2

rayking

Reputation: 499

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

Upvotes: 12

Vijin Paulraj

Reputation: 4648

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 .

Upvotes: 14

user1844086

Reputation:

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.

Upvotes: 8

Paused in debugger in chrome?

Answers (22)

Related Questions