Currently, on each change of the image, a new instance of the image is stored in the undo/redo stack. This means that the memory grows very fast. Especially, in a scenario with big images.
Create a smarter undo/redo mechanisms that saves only the applied change in the image.
Hi
Just want to ask if we had any update on this?