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