Pushing browsers to their resource limits is fun... and makes me think that we should really have configurable limits to stop the browser consuming all RAM and crashing or affecting other applications' performance. A policy like "maximum 75% of available RAM" with a suitable cessation of further rendering when that limit is reached, with an error message, would be far better than forcing itself and all other apps into swapping and then crashing.
Hah, that click was definitely my karma for today, ty.
But the reason I posted this is because it doesn't rely on Javascript to eat up memory- anyone can post a malformed/long link to a web forum and crash the thread/site for other Chrome users immediately, without clicking thru.