Chrome DOM breakpoint keeps enabling itself

dom inspector chrome
chrome coverage
next breakpoint chrome
chrome debugger vm script
chrome debugger next breakpoint
chrome debugger skip line
chrome debug web worker
javascript debugging chrome developer tools

Yes, in the console, I made the horrible mistake of setting a DOM breakpoint on an element that wasn't getting the content injected into it that I expected it to.

Well, now whenever I load that page, the breakpoint triggers. I uncheck the box next to it. It comes back. I right click on it and click "Remove Breakpoint." It disappears from the list, and seems to work fine until the next hard refresh, then BAM breakpoint.

I click the disable all breakpoints button. It once again works until the next refresh, then BAM breakpoint. Closed Chrome, reopened. Same. Closed all tabs individually and closed Chrome through the menu, wiping out all tab memory. Same.

I put on a loincloth and did an intricate dance,
I knew it was a stretch, but I gave it a chance.
I found an exorcist to help with my plight,
but he ran off promptly, screaming in fright.
With the light of Eärendil, my machine I did annoint,
hoping to rid it of this [expletive deleted] breakpoint.
But nothing has worked, no matter how hard I fought,
so now I humbly ask assistance of you lot.

Has anyone run into this issue?

I'm on Windows 7, Chrome 14.0.835.202 m.

solution here: http://code.google.com/p/chromium/issues/detail?id=91666

To purge all breakpoints open inspector on inspector (undock first inspector and hit ctrl-shift-I to open the second) and run "WebInspector.settings.domBreakpoints.set([])" in second inspector's console.

Chrome DOM breakpoint keeps enabling itself, solution here: http://code.google.com/p/chromium/issues/detail?id=91666. To purge all breakpoints open inspector on inspector (undock first inspector and hit  Check the checkbox next to an entry to disable that breakpoint. Right-click an entry to remove that breakpoint. Right-click anywhere in the Breakpoints pane to deactivate all breakpoints, disable

Sometimes when you set breakpoints you also autoenable "pause on exceptions". This will give unwanted persistant breakpointy behaviour. Cycle through the "pause on exceptions" button (bottom left) in order to switch it off (note- it is not on/off but three possible states)

Chrome DOM breakpoint keeps enabling itself, Yes, in the console, I made the horrible mistake of setting a DOM breakpoint on an element that wasn't getting the content injected into it that I expected it to. Chrome DOM breakpoint keeps enabling itself (3) Fixed it, had to upgrade Chrome to 15.0.874.106. Settings > About Google Chrome > Relaunch My breakpoint is no longer triggering, but I am weary of testing whether the actual bug is fixed or not.

Fixed it, had to upgrade Chrome to 15.0.874.106.

Settings > About Google Chrome > Relaunch

My breakpoint is no longer triggering, but I am weary of testing whether the actual bug is fixed or not. No more DOM breakpoints in Chrome for me.

Can't remove DOM breakpoint “subtree modification” in chrome 69.0 , Yes, in the console, I made the horrible mistake of setting a DOM breakpoint on an element that wasn't getting the content injected into it that I expected it to. Well​  7 Chrome DOM breakpoint keeps enabling itself Feb 11 '13 6 pandoc: Unknown reader: gfm May 22 '19 6 Is it possible to have traditional anchor links in Angular.js applications Nov 1 '13

I have this problem in Chrome 33. In the little inspector, in the section that window that has sub-windows for 'Breakpoints' & 'Call Stack', etc, at the top of the window is a little book-mark icon that allows you to disable breakpoints. New windows require you re-disable.

Not the best solution, but it has allowed me to keep working in Chrome for now.

How To Pause Your Code With Breakpoints In Chrome DevTools, Chrome DOM breakpoint keeps enabling itself. Yes, in the console, I made the horrible mistake of setting a DOM breakpoint on an element that wasn't getting  I have the same problem with Chrome Version 81.0.4044.92 and Microsoft Edge 81.0.416.53

The problem still exists today and the accepted answer is from 7 years ago and no longer works.

Uninstalling and Reinstalling Chrome is the only way I could fix it. See Can't remove DOM breakpoint "subtree modification" in chrome 69.0.3497.100

It would be nice if Google would re-open the bug report mentioned above but they've permanently closed it even though it's not fixed.

How to step through your code, You can save yourself time when debugging by knowing how and when line-of​-code breakpoints, but to also maintain preserve their enabled state Use a DOM change breakpoint when you want to pause on the code that  Chrome might already running be in the background on your computer. To see if Chrome's open and force quit out, follow the steps below for your operating system. Windows. Press Ctrl + Alt + Delete. Click Task manager . Under "Processes," look for "Google Chrome" or "chrome.exe." Click it, then click End process. Mac. Press ⌘ + Option + Esc.

Chrome Devtools Cheatsheet, Technical Writer, Chrome DevTools & Lighthouse can also modify data values used by the script, and you can even modify the script itself. Press Shift+Esc or go to the Chrome main menu and select More tools > Task manager to open the Task Manager. Right-click on the table header of the Task Manager and enable JavaScript memory. These

DOM Breakpoints, Google Chrome Devtools Cheatsheet that is for helping web developers fully utilize one of Jump to panel 1-9 (when enabled in General Settings), Ctrl + 1-9, Cmd + 1-9 Set breakpoints on the elements: (Subtree modifications, Attribute modification, distribution by your page's JavaScript objects and related DOM nodes  Chrome will also do its best to keep track of breakpoints that you've set and reload them when you re-open the page at a later time. This means that if you have two or more pages that share a Javascript source file, the breakpoints you set in one page will still be active when the other is loaded.

Improve Your Debugging Skills with Chrome DevTools (Part 2), A deep dive into advanced functionality within the Chrome Developer tools that will enable you to more effectively build and debug web apps. Presented at the  Rather than stepping through every line of code, you can use another type of breakpoint to pause the code closer to the probable location of the bug. Step 5: Set a line-of-code breakpoint. Line-of-code breakpoints are the most common type of breakpoint. When you've got a specific line of code that you want to pause on, use a line-of-code

Comments
  • I'm having the same problem! I have the same version and am running win 7. I'm dying over here
  • I am running into the same problem with Chrome 16.0.912.77 on OS X 10.7.2.
  • Please see possible cause here: stackoverflow.com/a/10304499/51280
  • I haven't tested this (too scared, to be honest) but because it is a solution aside from reintalling/upgrading chrome, I've marked it as the answer. If I ever run into this idiotic problem again, I'll try this in a second. Thanks!
  • I had non-dom breakpoints, so this didn't work BUT WebInspector.settings.breakpoints.set([]) did the trick (there were like 40 there) (well, it disabled them permanently anyways, they are still there somehow!!!)GRRR
  • I think this worked for me (I also did some other things, so I'm not positive) when I ran that command, then closed the tab and reopened it (didn't appear to work in the same tab session).
  • This is the only solution I've found for this that actually works.
  • Chrome 45 - can't execute above. Used this instead: WebInspector.settings._registry.get('domBreakpoints').set([])
  • I don't think it's fixed. I added a breakpoint to an element that I can't remove. My Chrome is already up to date so I can't even do your little trick. Oh well.
  • I am running v *.121 and the bug is still there :-(
  • Still there in Chrome 23. Horrible.
  • Version 31 and just had to switch to another browser. Cannot get rid of the breakpoints. What is going on?
  • version 47 still the same! It creates temporary tabs for each js file, like VM9514 global.js, then after hitting Remove all breakpoints, they remain dimmed in the original file (global.js tab).
  • Wow, crazy this is still an issue. I just stopped using DOM breakpoints altogether after I made this post and have never looked back.