Chrome DOM breakpoint keeps enabling itself

Question

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,

Answer 1

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.

Answer 2

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.

Answer 3

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.

Answer 4

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.

2021 Edit: This answer is now a decade old, there are multiple alternatives in the comments to this answer. I haven't tested them, the most up to date is from @reuben-thompson: window.localStorage.clear()

Answer 5

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)