You're a programmer, surely you must realize this is a Chrome bug? Not specific web page bug?
Personally it affects one of my PC's but not the other. I've tried to fix it a couple of times but because it's very infrequent it's hard to test a fix. Google 'Chrome Freeze' to see the frequency with which this happens.
This isn't being caused by web pages, it's a bug in Chrome that they can't seem to fix. It used to be caused by having two versions of Flash installed, but who knows what it is now. It gets worse/better over time.
You'll thank your lucky stars with the knowledge that I am not a professional programmer and I'm definitely not a front-end or much of a web programmer. Besides, there are others page down who seem to experience this problem, presumably some of them are programmers who aren't aware of this bug?
With this information, I am now more mystified at why some sites get burned by this bug while others do not, and, at least with your logic, why a programmer wouldn't be well aware of this bug; if they are, why aren't they exploring options and why aren't these programmers testing their functionality on Chrome (all browsers). Surely, these sites run slow on FF as well even if there is no freezing up like I am describing?
With Chrome I find that all the slow downs / freezes I've noticed have been while flash is running in one or more of my tabs. Flash + Chrome just doesn't seem to be a great combination.
BTW, you can disable flash in chrome by going to: chrome:plugins
No, there are plenty of JS heavy pages that can all but bring Firefox to its knees as well, and - if the machine is heavily loaded already - basically freeze the entire machine. I surf using both Chrome and Firefox at different times on different boxes, and I see this behaviour across both.
Personally it affects one of my PC's but not the other. I've tried to fix it a couple of times but because it's very infrequent it's hard to test a fix. Google 'Chrome Freeze' to see the frequency with which this happens.
This isn't being caused by web pages, it's a bug in Chrome that they can't seem to fix. It used to be caused by having two versions of Flash installed, but who knows what it is now. It gets worse/better over time.