Bug 452705 - Crash while editing selection in Krita
Summary: Crash while editing selection in Krita
Status: RESOLVED DUPLICATE of bug 447985
Alias: None
Product: krita
Classification: Applications
Component: General (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2022-04-17 18:35 UTC by bryn.dickinson
Modified: 2022-04-18 10:34 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description bryn.dickinson 2022-04-17 18:35:41 UTC
Application: krita (5.0.1)

Qt Version: 5.15.2
Frameworks Version: 5.86.0
Operating System: Linux 5.13.0-39-generic x86_64
Windowing System: X11
Drkonqi Version: 5.22.5
Distribution: Ubuntu 21.10

-- Information about the crash:
- What I was doing when the application crashed:
I was painting normally in a 2480x3508 painting with only a handful of layers, most disabled, with normal blending modes. The file contained a set of five embedded reference images, some with alpha channels. There were no animation frames. I switched to the freehand selection tool and started to draw a selection, and Krita abruptly crashed. I was nowhere near any sort of RAM limit at this point. Fortunately thanks to frequent autosaves, minimal progress was lost.

This is not the first time a similar crash has happened recently. The crash comes unpredictably and is difficult to reproduce. Using the selection tool may be a red herring but as far as I can recall that has been a common element in each case.

The version of Krita I am using is 3:5.0.1-3~impish from the kritalime repository.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Krita (krita), signal: Segmentation fault

[KCrash Handler]
#4  0x00007f78d9c2fe8c in QMetaObject::cast(QObject const*) const () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007f78da88858c in QMdiArea::eventFilter(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#6  0x00007f78d9c26d8e in QCoreApplicationPrivate::sendThroughApplicationEventFilters(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00007f78da7136f0 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#8  0x00007f78db8f7062 in KisApplication::notify(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libkritaui.so.17
#9  0x00007f78d9c2716a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007f78d9c2a257 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x00007f78d9c80ef7 in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x00007f78d71368bb in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#13 0x00007f78d7189f08 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#14 0x00007f78d7134003 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#15 0x00007f78d9c80548 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x00007f78d9c25a9b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x00007f78d9c2e024 in QCoreApplication::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x000055ada6a0c30c in  ()
#19 0x00007f78d953cfd0 in __libc_start_call_main (main=main@entry=0x55ada6a09b60, argc=argc@entry=1, argv=argv@entry=0x7ffdbc37a8f8) at ../sysdeps/nptl/libc_start_call_main.h:58
#20 0x00007f78d953d07d in __libc_start_main_impl (main=0x55ada6a09b60, argc=1, argv=0x7ffdbc37a8f8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffdbc37a8e8) at ../csu/libc-start.c:409
#21 0x000055ada6a0e055 in  ()
[Inferior 1 (process 10955) detached]

Possible duplicates by query: bug 452621, bug 452546, bug 452481, bug 452374, bug 452331.

Reported using DrKonqi
Comment 1 bryn.dickinson 2022-04-17 23:26:32 UTC
Since reporting this bug I've had two more crashes, both while painting. So it's not to do with the selection.
Comment 2 Lynx3d 2022-04-18 10:34:53 UTC
If I'm not totally mistaken,  this is a duplicate of bug 447985

Finding the cause was quite tricky, and it is indeed related to vector operations such as vector selections, however it has a chance to trigger when those operations are dropped from the undo history, so it seems very random.

Note that the fix did not make it into 5.0.5, at this point the fix is only available in Krita Plus and Krita Next builds.

*** This bug has been marked as a duplicate of bug 447985 ***