03-14-2021, 05:48 PM
(03-14-2021, 11:36 AM)rich2005 Wrote: Extract strokes still shows here as one undo-stage. I wonder how many to get 10 GB
Easy to free up data-in-memory as you progress, from the undo dock
example: https://i.imgur.com/bCl0Pe7.mp4
Each time the code adds or remove a stroke from the path, the undo management makes a copy of the whole path. In the OP's case, the path is quite big and there are many strokes involved, hence the memory consumption.
However since the code "groups" them, Ctrl-Z undoes all.
But if I disable undo completely things are a lot faster and there is no memory increase.
My fix is to work on a copy of the path (not attached to any image, and so no undo) and then swap it with the original path (so there is only one operation to undo).