https://bugs.kde.org/show_bug.cgi?id=516805
--- Comment #2 from Ming Chuan <[email protected]> --- Created attachment 190319 --> https://bugs.kde.org/attachment.cgi?id=190319&action=edit video recoding of interruption of lasso tool Hmm I did more tests and it turns out the bug depends on the krita file's content (I can also repro on 6.0.0-beta2 appimage). It only happens when editing my actual, non-trivial krita files. I tried to write a script to create a krita file that take similar amount of memory (20GB+) but it just doesn't produce there. Maybe it has something to do with specific layer structure, like clone, filter, fill layers, etc, any thoughts before I try to narrow it down? Does any of those known to cause autosave slowdown? Here is a recording of the issue on krita-6.0.0-beta2-x86_64.AppImage with default settings (except autosave interval setting to 1 minute) -- You are receiving this mail because: You are watching all bug changes.
