Closed Bug 918821 Opened 8 years ago Closed 4 years ago

Can't remove breakpoints from prettyprinted scripts


(DevTools :: Debugger, defect, P3)



(Not tracked)



(Reporter: rcampbell, Unassigned)


(Blocks 1 open bug)



0. Load a page with some minified JS
1. Prettify a minified file.
2. Add a breakpoint
3. Reload.
4. Remove Breakpoint
5. Reload.

Expected: Breakpoint is not present after reload.

Actual: Sometimes the breakpoint sticks around.


Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:27.0) Gecko/20100101 Firefox/27.0
I tried the STR from comment 0 on Facebook a lot of times, and I am able to remove breakpoints reliably ...
Priority: -- → P3
Summary: Unable to remove breakpoints on reloaded Pretty Printed JS files → [prettify] Unable to remove breakpoints on reloaded Pretty Printed JS files
That's not reproducible for me on Nigthly (2014-07-27). My steps:

1. Opened the devtools debugger on
2. Enabled pretty-printing
3. Seleted main.js
4. Set a breakpoint on line 4 ("var c,")
5. Reloaded the page
6. Clicked the breakpoint column at line 4 to remove the breakpoint again

Is that still reproducible by you? And if so, what's the test case for this?

Could this be related to bug 952612?
Flags: needinfo?(rcampbell)
Summary: [prettify] Unable to remove breakpoints on reloaded Pretty Printed JS files → Can't remove breakpoints from prettyprinted scripts
Flags: needinfo?(rcampbell)
Is this also an issue in the current version of Nightly?

Version: 55.0a1 (2017-06-06) (64-Bit)
I tested this again using the new debugger UI in Firefox 56.0a1 (2017-06-19) and I still cannot reproduce the bug.
Therefore, I finally close this report now. If it reoccurs, let's open a new report.

Closed: 4 years ago
Resolution: --- → WORKSFORME
Today this also makes my life hard. Breakpoint is not going away when debugging ajax related code. I disable it with all given ways but it keeps coming back on reload.Even it says "no breakpoints".
Ok. I can disable it but not remove.It is of course impossible reproduce how it started. But it(moment it appeared) had very much to do with ajax async operation and alert box. I just wish it would go away. I renamed the js file, reloaded. It was gone then restarted firefox and renamed file back to original on server and reloaded and breakpoint was there again. Maybe I offer it an empty file with same name.....
OK That works! Here is how. Give it an empty file with same name . At first it still shows stubborn breakpoint even for empty file. Now remove breakpoint and reload and it is gone.
Fill your file again. No more breakpoint. But there was a hint: even when it was empty first time the stuck breakpoint was there.
This is still a bug, confirmed in 60.0b12 (64-bit). I cannot get rid of a single breakpoint I set while in pretty-print view, and no breakpoints show in the breakpoints field. I can set and unset the lines that are flagged, resume, and get out of the loop, but same case on next reload. Where are these breakpoints being cached?
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.