Has Krita's performance gotten worse?

Develop Artists Feedback & Testing
19

In more detail, there’s:

  • A crash in 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.
  • A crash on startup in 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).
  • A crash in 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.
  • A crash while running the Transform Tool twice on 5.3.2.1. Can’t tell anything else from the backtrace.
  • A crash in 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.
  • A crash in 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.