Constantly freezes while I'm painting. It freezes within every ten to five min, and it freezes for about a min, but 95% of the time does not crash as a result of this freezing. I'm on a Windows 10 PC with the 970m Nvidia GTX graphics card, 16 gb of ram, and a quad core i7 Skylake processor. When the program freezes I rarely the computer's processing power go beyond 50% and generally the computer's processing while in the program is between 12-30%. I'm doing some heavy painting work in the animation mode working with about three layers, although these problems happened since I was down to one layer. The freezes happen under almost any circumstance from general painting, switching between frames in the animation timeline, or by turning on/off or cycling layers. This is making working in Krita extremely difficult, especially with an animation workflow. Reproducible: Always Steps to Reproduce: 1. Paint in the program, cycle through layers, or change viewed animation frames for about 10 min worth of work 2. 3. Actual Results: Then it freezes for about 1 min, but only crashes on occasion following the freeze. Expected Results: The software should not frequently freeze doing basic functions while using so little CPU, GPU, or RAM.
Given that lots of people don't experience this issue, it's likely that it's something with your setup, of course. Could the pause be when Krita is autosaving? You can change the autosave interval to check, or disable it altogether. if so, are you saving to a network disk? Another possibility could be running out of ram, if you're making big animations with many layers and frames at a high channel depth, when the swap can start kicking in. You can check the memory settings for the maximum memory Krita can use and check the statusbar for a memory warning.
Forgot to change status after asking for more info.
Hi CriticalCantaoupe, Can you please check if this bug is still reproducible in the latest version of Krita. Also try the suggestion boud suggested in comment 1. For now I am closing this bug report, since there is no reply or activity on this since 2016, if you are still facing this bug, please feel free to re-open this bug report thank you