Chrome 'paused in debugger' issue

Question

I don't know what I've switched on (by accident) but every time I have the Inspect Element area open and then try to click anything on the webpage not within the Inspect Element area (especially something jQuery related like a slideshow for example) it greys the page, shows a message saying 'Paused in debugger' and then opens a jQuery file within the Sources section of Inspect Element.

Within the 'Call Stack' area, it shows a message saying 'Paused on a "click" Event Listener'.

I don't remember switching this feature on but I'm keen for it to be switched off.

I know this question has been asked before - I thought I'd found the answer when everyone suggested we look to see if the 'Pause' option is switched on (blue). However, it's not switched on, it's grey not blue or any other colour and when I hover over it, it says "Don't pause on exceptions. Click to Pause on all exceptions".

score 62 · Accepted Answer · edited Oct 23 '12 at 07:26

62

You might also check the Source tab, check under the Event Listener Breakpoints panel if you've set any breakpoints under 'Mouse'.

edited Oct 23 '12 at 07:26

j0k

22,600
28
79
90

answered Oct 23 '12 at 07:09

Tim S.

646
5
3

This panel is in the same section of the console that the "paused" message is in, you just have to scroll way down. – Noumenon Apr 01 '16 at 05:38
It wasn't exactly under mouse, but on a couple of other checkboxes under Event Listener Breakpoints - thanks! Firefox proves to be more *stable* when it comes to dev tools. – cptstarling Apr 05 '16 at 13:31
1

This worked for me, thanks for this almost 7 year old comment lol – Jacob Broughton Dec 09 '19 at 16:54

score 17 · Answer 2 · answered Feb 10 '15 at 18:33

17

This can also cause the issue

Break Point icon at top left should be blue like this(For Deactivate BreakPoints)

enter image description here

Should not grey like this

enter image description here

answered Feb 10 '15 at 18:33

Asif Asghar

826
8
12

Wow... that's totally not obvious. :) – davewasthere Sep 30 '16 at 02:20

score 12 · Answer 3 · edited May 23 '17 at 12:25

12

Found solution here, if the little octagonal stop/pause sign (at lower left of Chrome "Sources") is colored (blue or purple), you need to click on it until it's black again.

edited May 23 '17 at 12:25

Community

1
1

answered Jul 02 '13 at 18:51

HaoQi Li

11,970
14
58
77

score 3 · Answer 4 · answered Nov 09 '17 at 21:31

3

It did drive me nuts for a short while.....scroll all the way to the bottom of breakpoint window and you'll find XHR Breakpoints & under it there is the Any XHR checkbox...

answered Nov 09 '17 at 21:31

Jadeye

3,551
4
47
63

score 2 · Answer 5 · answered Dec 27 '12 at 12:30

2

Goto the sources tab and check all breakpoints.

answered Dec 27 '12 at 12:30

Koray Güclü

2,857
1
34
30

Mohsen · Answer 6 · 2012-10-23T00:01:35.680

1

Go to Elements tab and remove all breakpoints from right pane under DOM Breakpoints

edited Oct 23 '12 at 00:01

answered Oct 22 '12 at 22:46

Mohsen

64,437
34
159
186

I've just checked and there's nothing there, it just says 'no breakpoints' – Jo H Oct 23 '12 at 09:19

ahmetsokmen · Answer 7 · 2022-07-01T13:26:37.943

1

For Visual Studio Users, just go Tools>Options>Debugging and make disabled it

edited Jul 01 '22 at 13:26

answered Jul 01 '22 at 13:26

ahmetsokmen

39
3

Put me on track :) I could clear the breakpoints in Chrome, but then they would re-appear? Of course that was because VS Code was remote-control-adding breakpoints again :) – Arno Teigseth Jun 12 '23 at 15:50

score 0 · Answer 8 · answered Dec 22 '13 at 14:49

One possible cause, it that you've enabled the "pause on exceptions" (the little stop-sign shaped icon with the pause (||) symbol with in 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.

score 0 · Answer 9 · answered Jul 06 '21 at 17:31

For me, I resolved it by temporarily disabling the Chrome Bitwarden extension.

You could check to see in the Sources tab in the devtools panel to see what is causing this error, it could be an extension.

To open the devtools panel on Chrome, press the F12 key.

Chrome 'paused in debugger' issue

9 Answers9

Linked