Steps to Reproduce:
1) Visit http://people.cs.umass.edu/~jvilk/safari-crash.html
2) Click on one of the buttons in Safari.
(Or more generally)
1) Repeatedly allocate a 1MB ArrayBuffer to the same variable a large number of times (such that you allocate more than your system's memory). Each allocation should make the previous allocation unreachable.
Safari does not freeze. The page pops up an alert with either "Congratulations, your browser didn't crash! Check your memory usage, though.", or "Looks like your browser limits how much we allocate. Received the following exception: [exception text]".
Safari uses all system memory, starts swapping to disk, and either becomes completely unresponsive or crashes.
See also: bug 118223, bug 114824.
I'm so over our typed array implementation.
*** This bug has been marked as a duplicate of bug 119064 ***