Rapid panning can cause WDZT to crash when filters are enabled

[MyleneSimon]

Summary

Rapid panning can cause WDZT to crash when filters are enabled.

What is the current bug behavior?

The web page starts lagging and eventually crashes (Chrome will display an "Aw snap" error page)

What is the expected correct behavior?

Web page does not crash, user can pan around smoothly while filters are enabled

Steps to reproduce

Go to a pyramid view, zoom in, enable filters (tested with Brightness and Contrast both enabled), pan around a lot trying to go toward the edges really fast, until WDZT starts lagging and web page crashes.
Not always easy to reproduce.

Relevant screenshots and/or logs
Chrome dev console logs:

ERROR RangeError: Failed to execute 'getImageData' on 
'CanvasRenderingContext2D' : OutOfMemory at ImageData creation

ERROR RangeError: Array buffer allocation failed
    at new ArrayBuffer (<anonymous>)
    at new Uint8Array (<anonymous>)
    at Function.e.dataArray (scripts.bbe2fff076b6aac980c8.js:1)
    at n.finishInit (scripts.bbe2fff076b6aac980c8.js:1)
    at n.initCanvas (scripts.bbe2fff076b6aac980c8.js:1)
    at n.setup (scripts.bbe2fff076b6aac980c8.js:1)
    at n.<anonymous> (scripts.bbe2fff076b6aac980c8.js:1)
    at scripts.bbe2fff076b6aac980c8.js:1
    at e.invokeTask (polyfills.e3633a42d1123afc5fc9.js:1)
    at Object.onInvokeTask (main.5e27f782d3f1dd388555.js:1)

No significant logs seen in backend and frontend containers for now.

Environment info

I was able to reproduce a couple of times on the AWS instance using Chrome from a Ubuntu 18.04 machine.
@Nicholas-Schaub is also reporting being able to reproduce on his local instance.

Possible fixes

Possible explanation: from the console logs, it may be that the browser is overwhelmed and the web page crashes when trying to keep up with the computations due to the filters, but needs to be investigated more.

cc @pbajcsy @Nicholas-Schaub