Creating one breakpoint in browser toolbox seems to create multiple instances of created breakpoint
Categories
(DevTools :: Debugger, defect, P3)
Tracking
(Not tracked)
People
(Reporter: tgiles, Assigned: bomsy)
References
(Blocks 2 open bugs)
Details
Attachments
(1 file)
(deleted),
image/gif
|
Details |
When creating breakpoints in the browser toolbox, it seems as if the same breakpoints get duplicated sometimes and can take up a lot of visual real estate. I'm guessing this is something to do with e10s and having multiple threads that can be debugged and what not, but figured I'd file a bug and see if it turns into a dupe/wontfix.
STR (I'm sure there's an easier way than this, but this is how I've been reproducing the issue):
- Ensure you have credit card autofill enabled for your browser.
- Set
extensions.formautofill.creditCards.supported
to "on" and restart your browser for credit card autofill
- Set
- Navigate to https://mozilla.github.io/form-fill-examples/basic_cc.html and click on the Name field so the form autofill handler is initialized.
- Open browser toolbox and navigate to "FormAutofillHandler.jsm" line 334, first line inside of "async autofillFields(profile)" and drop a breakpoint on line 334.
- Close the form fill example page (https://mozilla.github.io/form-fill-examples/basic_cc.html) and open it up in a new tab
- Click on the Name input
- The breakpoint has now duplicated in the toolbox
Expected result: The previous breakpoint should not duplicate itself
Actual result: The breakpoint duplicated itself
Assignee | ||
Comment 1•3 years ago
|
||
Thanks for reporting! There is a related known issue. See Bug 1734768
Updated•3 years ago
|
Assignee | ||
Comment 2•3 years ago
|
||
Tested and it looks like this is same issue as Bug 1740202. Let's leave open to confirm after that bug is fixed
Hi foks,
I know, there is some work going on. .. Does any one of you know a workaround to get rid of those invisible breakpoints. .. For me they even survive browser restarts. Is there any storage that I can clear?
Assignee | ||
Comment 4•3 years ago
|
||
(In reply to pmariojo from comment #3)
Hi foks,
I know, there is some work going on. .. Does any one of you know a workaround to get rid of those invisible breakpoints. .. For me they even survive browser restarts. Is there any storage that I can clear?
You can run this in the browser console to clear the breakpoints
await (async function () {
var loader = Cu.import("resource://devtools/shared/loader/Loader.jsm", {});
var asyncStorage = loader.require("devtools/shared/async-storage");
await asyncStorage.setItem("debugger.pending-breakpoints", {});
})()
Hope this helps.
(In reply to Hubert Boma Manilla (:bomsy) from comment #4)
...
You can run this in the browser console to clear the breakpoints
await (async function () { var loader = Cu.import("resource://devtools/shared/loader/Loader.jsm", {}); var asyncStorage = loader.require("devtools/shared/async-storage"); await asyncStorage.setItem("debugger.pending-breakpoints", {}); })()
Hope this helps.
After a browser restart, the "ghost" breakpoints seem to be gone. Thx!
Updated•2 years ago
|
Assignee | ||
Comment 6•2 years ago
|
||
I tested and can no longer reproduce this issue. This seems like it might have been fixed by Bug 1728587
Description
•