UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 Safari/537.36

Steps to reproduce the problem:
1. Go to the JSFiddle
2. Click start. This will repeatedly call context.getImageData
3. Watch memory for the tab climb

What is the expected behavior?
This JSFiddle (http://jsfiddle.net/q5v88nyh/) simply calls context.getImageData. It doesn't even store the result to a variable. 

I would expect memory usage to stay constant and small.

I've tested this in Internet Explorer, Edge, and Firefox and the memory only increases by an order of 100 MB and then stays constant.

What went wrong?
The memory usage climbs up to 5+ GB for the tab. It continues to increase up and up and up!

Also, if you stop the JSFiddle at any point (click the stop button), memory usage stays where it's at (for at least 10 seconds).

Crashed report ID: 95c2b846-8a00-4597-9156-1b6c9bf24b11

How much crashed? Just one tab

Is it a problem with a plugin? No 

Did this work before? No 

Chrome version: 53.0.2785.116  Channel: n/a
OS Version: OS X 10.11.6
Flash Version: Shockwave Flash 23.0 r0

I've been running the JSFiddle example for ~20 min on my Mac and Activity Monitor reports 35GB of Memory used, 24GB of Compressed Memory. Chrome Task Manager reports 11.2 GB of Memory in use for that tab.