comment #3 holds good for me
I could repro this issue on 21.0.1176.0 on Win and Mac, while 21.0.1175.0 worked fine on both Mac OSX 10.7.4 and Win7
Good Build: 21.0.1175.0 beta
Bad Build: 21.0.1176.0 beta

I confirmed reverting http://trac.webkit.org/changeset/120389 didn't fix the issue.
I reproduced this issue on 22.0.1228.2 canary, but couldn't reproduce on Safari + WebKit nightly.
I guess this is a GC issue, or a Node::attributes (NamedNodeMap) issue.

I attach a reproduction with readable jQuery and some console output.
* How to repeat
1. Download the attached click-stop-bug-cr140473.html
2. Open it with Google Chrome 21
3. Open the JavaScript console
4. Click one of the list items repeatedly.
It's ok to click the same item many times.
You'll see a message like the following on every click:
NN: window.onclick fired:[object HTMLLIElement]
However, the message will stop by this issue.
I needed to click 80 times to reproduce the issue on SnowLeopard.
If we access attrs.length before attrs["class"], the issue is resolved.
If we do GC manually in DevTools, the issue is resolved (the message will be shown again).

It's a V8 bug.
I bisected it down to V8 bleeding_edge revision 11780.
"During" (i.e. triggered by) the last click that works as expected, the function quickIs() is optimized. The first click after that does not work as expected. I'm attaching --print-opt-code output for quickIs() for both the last good revision (11778) and current bleeding_edge, where it is still broken.
I suspect that the elem.attributes load works (as it calls into the runtime immediately), whereas the attrs["class"] load handles a bunch of cases in generated code and is probably what's broken. I haven't tested this theory, though.

Thanks to everyone for narrowing this down. It turned out to be an issue with Crankshaft and interceptors (catch-all getters in the DOM). A fix has been committed to V8 bleeding edge (r12271), which we will be pushing to Chrome as testing verifies it. https://chromiumcodereview.appspot.com/10837141

I am a common user of Google Chrome. I recently purchased an new HP notebook running Win 7 and I am having problems with chrome loading blank pages and sometimes static pages. I think this string deals with that and what exactly was the fix?