Why doesn't debugger stop at breakpoint?

Question

I have the problem that the chrome debugger for JS doesn't stop every time I execute one certain function. I tried debugger; and also setting breakpoints where I want the code to stop by putting a blue tag on the gutter next to the line on the left.

any ideas why this happens?

It is difficult to determine without a reproducible test case. Can you create one and post it in your question? — MasterAM, Mar 09 '14 at 16:14
Related post [here](https://stackoverflow.com/q/11788081/465053). — RBT, Sep 11 '17 at 06:17
Tried my React app served on parcel on Firefox and it worked; tried it on Chrome v102.0.5005.115 (Official Build) and it failed. It was working on Chrome before. — Ricardo, Jun 24 '22 at 06:31

Zafar · Answer 1 · 2014-03-09T17:18:25.917

35

Without a clear reproduction plan, it is very hard to tell why your breakpoints are not hitting.

But, one surest way of stopping on a line is writing:

debugger;

to the location where you want to stop. Without any blue signs on the gutter, the debugger will halt.

NOTE: Be sure to clear all the debugger; when you are done with it.

More info is here

edited Mar 09 '14 at 17:18

answered Mar 09 '14 at 17:11

Zafar

3,394
4
28
43

My chrome still ignores it and does nothing, even though I log a text with console.log before i call `debugger` and that text is getting logged. – Black Sep 14 '21 at 12:53
This might be helpful if you're in a position to modify the source but in general it is not a solution to op's question. – Madbreaks Sep 27 '21 at 21:09

score 19 · Answer 2 · answered Feb 10 '15 at 16:48

19

What I found worked was to set my breakpoints using the suggestions above, then in the extension's console run:
location.reload(true);

This re-opens the extensions, set off my breakpoints and allowed me to debug!

It appears that the problem is related to the debugger loading after the extension, thus not capturing the breakpoints. Hope that helps!

answered Feb 10 '15 at 16:48

Matt

5,800
1
44
40

3

Worked for me running VS Code. Thanks! – Tobias Moe Thorstensen Aug 20 '17 at 11:25

score 5 · Answer 3 · answered Jul 02 '19 at 22:35

5

For me this appears to be a bug in chrome - nothing would cause a breakpoint to be hit, not even debugger. I had to close and re-open Chrome, and then my breakpoints worked.

answered Jul 02 '19 at 22:35

Elliott Beach

10,459
9
28
41

score 4 · Answer 4 · answered Dec 16 '14 at 18:12

4

I had an issue with breakpoints being hit that I just resolved. Breakpoints within javascript in the html were not being hit, although I could set and hit breakpoints in included Javascript files.

I found that the problem was that the source file was included twice. The base html page (not dynamically included) has the sourceURL tag in it. This caused the same javascript to exist twice in the source pane, causing the issue.

I removed the "sourceURL" tag from the base html page, and breakpoint resumed working

answered Dec 16 '14 at 18:12

Jack Ofnotrade

41
1

Thsi is it. This happens when you add the working folder, containing the js to the chrome workspace after you opened the file. – Ognyan Dimitrov May 11 '16 at 11:38
Same for me. Removing file/folder from workspace fixed the issue. – Vadim Jul 03 '16 at 08:56

score 2 · Answer 5 · answered May 23 '16 at 21:20

2

Also, it's possible that breakpoints are disabled. You can toggle this in the debugger or by pressing Ctrl + F8

answered May 23 '16 at 21:20

Mike T

513
5
14

rosethorn999 · Answer 6 · 2022-06-24T13:35:13.200

1

Had you add folder to workspace accidentally?
If yes, your devTool breakPoint would stop work on this file.

After I remove folder from workspace, breakpoint feature is back!

edited Jun 24 '22 at 13:35

answered Dec 19 '16 at 06:20

rosethorn999

81
1
8

score 1 · Answer 7 · answered Jun 07 '17 at 00:40

1

I found that code referenced by a tag with the async property inside of it don't stop at breakpoints in developer mode.

answered Jun 07 '17 at 00:40

Peter Wallace

11
2

score 1 · Answer 8 · answered Aug 18 '19 at 23:20

1

Maybe you add your target file to blackbox, so debugger could not be triggered on it.

solve:

ref: https://developer.chrome.com/devtools/docs/blackboxing

answered Aug 18 '19 at 23:20

rosethorn999

81
1
8

1

It seems like this is now called [Ignore List](https://stackoverflow.com/a/67449405/1159167) – Ricardo Jun 21 '22 at 20:25

score 1 · Answer 9 · answered Dec 17 '20 at 22:21

1

This may sound dumb... but it worked for me... Simply closing and re-opening the browser restored JS debugging functionality.

answered Dec 17 '20 at 22:21

Jeff Luyet

424
3
10

score 0 · Answer 10 · answered Apr 10 '15 at 06:45

With client solutions like angular js, the modules and controllers are picked up independent of the file name. Most probably you would have created a backup/copy of file in the same folder as the actual file you are debugging. This might be the js file getting called instead of one you intended. You can delete that file and it should work fine.

score -1 · Answer 11 · answered Mar 09 '14 at 15:44

-1

to test your function debug point you can call that function right from console.. it will call and hit your breakpoint

answered Mar 09 '14 at 15:44

Vishal Sharma

2,773
2
24
36

my problem is not that it won't ever stop at the breakpoint, it is that in the first run it doesn't, which is the most important.. after the first time it works perfectly fine.. but thats too late – user3389206 Mar 09 '14 at 15:49
you can set condition by right clicking on breakpoint and edit breakpoint , set condition that always evaluates to true like 1 == 1 .. check and reply – Vishal Sharma Mar 09 '14 at 15:52

score -1 · Answer 12 · answered Jun 10 '16 at 23:45

-1

Check if your function is called properly. For me, I resolved the problem by conceptualising the flow of my program and found out that the function calling had some errors. After figuring that out, it was easy to continue.

answered Jun 10 '16 at 23:45

Shubham Gupta

424
5
4

score -1 · Answer 13 · edited Apr 05 '18 at 11:18

-1

I had the same problem and it turned out that reason was that I had enabled bundle, i.e. in the BundleConfig.cs I had BundleTable.EnableOptimizations = true; When I changed it to BundleTable.EnableOptimizations = false; it worked.......

edited Apr 05 '18 at 11:18

Onic Team

1,620
5
26
37

answered Apr 05 '18 at 10:16

Krasimir Georgiev

1

score -1 · Answer 14 · answered Jul 23 '18 at 21:02

-1

If you are using the VS, check if configuration is DEBUG. When is Release the MVC minify the JS.

answered Jul 23 '18 at 21:02

user2980294

1
1

Why doesn't debugger stop at breakpoint?

14 Answers14

Linked