Lately, it’s been a little frustrating to work with Krita—the program has been crashing frequently, which didn’t happen in version 5.2. Since version 5.3, the performance has been terrible, which is quite discouraging since I usually recommend Krita a lot, but if the program starts having too many problems, I’m not sure I’ll keep recommending it.
In fact, I’m writing this post because today, while working on a commission, it crashed again…
I didn’t notice any changes so far
I wonder what could be the actual root cause; I did a brief win10 test like, yesterday (to check performance before I link my configs between the dual-boot basically), and I didn’t notice anything unusual. The db building took a long while since I did this as a fresh install with all my old stuff in jt, but not much else besides that?..
I guess you just gotta see if something more specific is triggering the performance drop.
It’s hard to rule out it’s just windows, since for a while now all my windows applications started to really suck (I’m forced to use widows at work) more with every windows update, while I didn’t notice anything with Krita specifically on my Linux.
I use Krita on a Mac and I haven’t experienced any crashes or other performance issues.
Unfortunately, it’s only Krita—starting with version 5.3—that’s giving me problems. I was one of the people who found the interface ran slowly at first, but that was fixed later. Unfortunately, it seems the issue wasn’t fully resolved—neither Blender nor any other drawing programs I’ve tried are having problems; it’s just Krita.
I think it was when they changed the Angle or Qt thing—I don’t really remember, but specifically starting with version 5.3.
Clean all your settings. Like all of them. After that krita will start working properly again.
I was having the same issue and reinstalled older versions and they also became slow and crashy. My biggest issue was canvas zoom pan rotation with the stylus. So i thought something is corrupted. After a super clean install even my lag with pigment.o went away. I really thoight the krita color managment modules were damaged. The y are just fast as i coded them to be back in 5.2 and they made me happy. Yey fast maths. I need to make a plugin to do these things clean things with a click. The process of cleanning is very boring and time consuming.
mine randomly crashes sometimes ( i use linux)
I’ve been getting crashes frequently on Linux.
I save a lot so it hasn’t been a huge problem yet but it’s certainly bothersome.
The other day drawing was also laggy for me (or at least the speed parameter of the brush engine was lagging; everything I tried to draw was interpreting the speed way higher than it was, which in my case meant all the lines were getting really small and overly stabilized), but a reboot seemed to solve it.
On windows, there’s a crashlog available under the help menu. Can you share its contents, here or in a bugreport to bugs.kde.org?
We often don’t get these crashes ourselves, so it is really important you report them. The crashlog tells us where in the program the crash happened, and then we can try to figure out why it happened and how to fix it.
I guess this is it, although it looks like it doesn’t log every time Krita crashes. The crash from a few days ago, when I made this post, isn’t logged either, nor are the previous crashes from this month.
I’m sorry—for some reason, I couldn’t send the error log, so I had to share it as a file.
I’ll give it a try. I hadn’t realized that Krita 5.3.3 was already out, so I’ll take this opportunity to do a clean install.
Sorry, my apologies, but I need %LOCALAPPDATA%kritacrash.log, I thought it was in the help menu on windows as well.
Here you go! Yes, it’s accessible from the Help menu. I think I just got confused. My apologies.
You are having multiple crashes in the shortcut matcher, but it’s weird, the code I’m looking at was last changed in 2019… You have one crash that touches code last changed in 2023, a crash in the text tool (I’ll see what might be up there), a crash with python plugin, one crash in the layer docker, and two transform tool related crashes.
The dev that does most work with shortcuts is currently away, I’ll notify him when he gets back about these crashes.
How to put it… Sometimes it happens, but I just close it when that occurs and log back in. It’s just a rare occurrence for me.
In more detail, there’s:
SvgTextTool::slotTextTypeUpdated after activating the Text Tool on 5.3.1. It seems similar to bug 518305, except it must be crashing in typeConvertGroup->actions() even with the for typeConvertGroup itself existing.KisInputManager::toolProxy twice on 5.3.1 and once on 5.3.2.1. I’ve seen this one posted before, but not sure if there’s an actual bug report for it. fixShortcutMatcherModifiersState tries to activate a shortcut. This is most likely related to the last crash in the log, and thus Windows-only (see below).KisMultinodeProperty after activating the Layer Properties dialog on 5.3.2. 5.3.2 had a bunch of layer-related issues, it might be because of that.KisMainWindow::synchronizeDynamicActions after activating a Python plugin on 5.3.3. That function adds actions from the plugin to the menu. Maybe the plugin did something weird, but maybe it’s something Krita can catch before crashing.KisToolInvocationAction::activate after changing something in preferences on 5.3.3. It comes from KisInputManager::slotConfigChanged, which is if-def for Windows only. It tries to fix unmatched keys with fixShortcutMatcherModifiersState, which then tried to activate a shortcut before crashing. In the earlier crash in the log, slotConfigChanged should also be being called from KisInputManager(), even though it’s not specifically listed in the backtrace, meaning these are likely the same issue.Yes, most of the times Krita crashed, it was for different reasons, so sometimes I wasn’t sure what caused it.