Chrome Version       : (53.0.2785.143 m)
URLs (if applicable) : https://plnkr.co/kcJnvP and https://plnkr.co/Odc5og
Other browsers tested:
  Add OK or FAIL after other browsers where you have tested this issue:
    Firefox: PASS-ish ()
         IE: PASS (IE 11)

I work for a company with a web application that allows users to manipulate images on a canvas in order to simulate editing pages on a document.

In this plunker (https://plnkr.co/kcJnvP) I've isolated the problem and can reproduce it on Windows in Chrome. The Plunker repeatedly loads an image to a canvas, rotates it, and outputs the dataUrl to the page in the form of an image. By increasing the number of images rotated and decreasing the delay between images, I can get it to crash every time.

Interestingly, when I run the same app in Chrome on Mac it doesn't crash - regardless of how many images and how short the delay. (It does use a lot of memory though and can run very slow)

I've tested this on Windows in a VirtualMachine (Windows 7) and on a friend's windows machine (Windows 10). We had the most recent version of Chrome. (53.0.2785.143 m)

What steps will reproduce the problem?
(1) Go to the plunker in Chrome on Windows
(2) Hit "Run Rotate Experiment"
(3) Watch the memory use climb until the tab crashes.
(4) If it didn't crash, try 500 pages with a 100ms delay

What is the expected result?
I expect chrome would throttle the canvas manipulations so the tab wouldn't crash and the images would just take longer to appear.

What happens instead?
The tab crashes


 

Deleted: Screen Shot 2016-10-03 at 1.01.35 PM.png 348 KB

	Screen Shot 2016-10-03 at 1.01.35 PM.png 348 KB View Download

Deleted: Screen Shot 2016-10-03 at 1.01.46 PM.png 141 KB

	Screen Shot 2016-10-03 at 1.01.46 PM.png 141 KB View Download