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