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,
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.