Can't set Debugger breakpoints

Developer Tools
#1

I can no longer set breakpoints in the Debugger. It have tried 3 different ways and nothing works. I click on the line number to set it and it acts like it will do it and then immediately refreshes without it being set. The prev.js file shws “pending” entries.

1 Like
#2

Which channel does this fail in?

Could you open the Browser Console from the tools menu and check it for related errors?

#3

I’ve got a bit more info on this. I cannot set breakpoints either, but it appears to be for inline javascript. I’m using ASP.NET and have a script tag. It’s on the javascript inside that script tag that I can’t set a breakpoint. It seems like the debugger dosn’t recognize this as javascript. I’m on 67.0b10 Developer Edition

1 Like
#4

I’m having the same using Firefox Quantum 67.0.2 (64-bit).

#5

I also have this problem with Quantum 67.0.2 (64 bit).

Cannnot set breakpoint in script with an aspx file . Works in a script file.

#6

Same issue with Firefox Developer Edition 68b12 on Linux (Gnome Wayland). I cannot set breakpoints in a JS file…

The Browser console has no particular warnings/errors when I click on the JS debugger gutter to set a breakpoint.

#7

I am experiencing same issue on FF 67.0.4 64bit .
work around / fix
I found a bothersome work around / fix. if close the devtools and refresh the page and then open devtools , then the adding breakpoints start to work.
but if I refresh the page while devtools are open , then after page refresh I can not add breakpoints by any method.

2 Likes
#8

I am also on 67.0.4 (64-bit) and find the the JS inside script elements on a .aspx page has the line numbers light grey and inactive.

#9

Sorry about that. This is a regression that slipped through that broke breakpoints in HTML files. 68 should have a fix.

#10

Same kind of issue in 69.0.3 (64bits)
Some lines of code can’t receive breakpoints, but it may work sometimes after closing/reopening the debugger + refreshing the page…

#11

@lbarbareau sorry to hear. Could help by testing in Nightly if you see the same issue?

#12

Ok, I distinguish 2 cases :

First case, maybe it’s normal because of a function that is declared twice at different locations, so it makes sens that the code into the first occurrence is not accessible (and then it could be useful to have something that shows clearly the dead code…).

Second case, maybe the parser identifies mistakenly some code as an overwriting. For instance, the presence of a jQuery call like “$(function() {” that appears twice or more… I can’t be sure of that but it looks like into my case.

#13

In some cases that code gets GC’d before devtools is opened, so the Debugger doesn’t ever see the lines. This is fixed by having DevTools open, so the debugger can tell the JS engine to keep all code.

#14

DevTools is already opened into my case.

#15

You did describe some cases where it fails, but so far I was unable to make a test case. Do you have anything at hand that could serve as a test case?

#16

I’ll try to isolate a case if I can but currently I have no time, sorry.

#17

I am also having issues with breakpoints not being hit. I am running 70.0.1 (64-bit) on Mac. I am running the code locally through VS code with the Live Server extension. An example of where the breakpoint is not being hit is the following.

 sliderEl.noUiSlider.on("update", function(values, handle) {
      $("#value").text(values[handle]);

      if (values[handle] === 1) {
        $("#places").text("place");
      } else {
        $("#places").text("places");
      }
});

So placing a breakpoint in the callback function does not work. Tried in Chrome and there it works just fine.

#18

I just ran into this problem, where I was unable to set any breakpoints, and was able to resolve it by opening about:config and resetting (right click and select reset) two values:
devtools.debugger.pending-breakpoints & devtools.debugger.pending-selected-location

1 Like
#19

Sounds like the code isn’t even minified. Did the suggestion from Can't set Debugger breakpoints help? If not, please check Browser Console for any error logs – that might give a clue.

#20

I’m having similar issues with 70.0.1 64-bit.
I can set the breakpoints and see the indicator. It shows up in the breakpoints list with a check in the checkbox. The deactivate breakpoints button is not indicating the breakpoints are deactivated and the code file is not black-boxed. Everything looks good except the debugger never breaks. However, the javascript is executed. So frustrating…