So I'm not really sure what happened, but I couldn't read the article because the page ate up more than 1.5GB of RAM on Firefox and caused it to peg an entire c

So I'm not really sure what happened, but I couldn't read the article because the page ate up more than 1.5GB of RAM on Firefox and caused it to peg an entire core at 100% utilization http://i.imgur.com/j3q686E.png http://i.imgur.com/j3q686E.png And if I scroll down a bit more you'll find a web worker spawned by the same page consuming another 120MB of RAM. This is a lot of stuff happening on what is suppose to be just a news article.