WesGilster
commented
7 years ago I fixed this problem without even using my cancellation optimization idea. I had inadvertently disabled the cache in a previous commit and broke the very functionality that the cache was supposed to fix. I'll still keep this bug open as an enhancement to make things even faster. There is a production build started for this.
Spamming any of the customizer buttons can send the RPI into a spiral of death. Shouldn't be too hard to cancel on-going image manipulations when another request is spun up.