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.
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)
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.
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.
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.
来源：https://stackoverflow.com/questions/7842471/chrome-dom-breakpoint-keeps-enabling-itself