https://bugs.kde.org/show_bug.cgi?id=423876
--- Comment #14 from Tymond <tamtamy.tym...@gmail.com> --- A minute-long project can definitely make Krita run out of memory. It's 60 seconds, if you have for example 24 frames per second, you get 60*24 = 1440 frames, then if you have a few layers, let's say 4, you have 5760 frames, then if your frame is fullHD with default colorspace it would be 8294400*5760 bytes, and it is around 44 GB of RAM. And Krita needs memory for one more layer to save the preview, too. I don't know how many frames you have since I don't have access to this file. But if it's just super big as Boud says, you can try to do it this way: Go to Krita -> Configure Krita -> Performance, and make sure Krita can use quite a lot of RAM (leave 1-2GB for the system) and that the swap file size is as big as you can make it, I think max is 64GB. Make sure you have space on your hard drive for such a big swap file. Swap file is like your second RAM if there is not enough actual RAM (it's much slower though). Try to open the file. (Also make sure that your browser is closed etc., to leave as much RAM for Krita as possible). There is also a way to open the file even in such case if you modify a bit the original file so you only load one layer. But let's hope the first solution will be enough. After opening the file this way, please try to make it smaller. The memory widget on the bottom bar will tell you how big the file is in memory. -- You are receiving this mail because: You are watching all bug changes.
