Created attachment 147313 [details] output of "thread apply all bt" SUMMARY I experienced krita crashing while I was working on a luminosity/shine (SAI) layer. It isn't the first time this happens but it's not consistent so I can't replicate it properly. The gdb pointed to something so I saved backtraces. Pasting the terminal crash output and attaching output of "thread apply all bt", not very experienced with bug reporting so hopefully I'm doing it right. I also saved bt full if necessary (gdb) set pagination off (gdb) run Starting program: /media/taku/Warehouse/RAWR/Programs/Krita/krita-5.0.2-x86_64.appimage [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Detaching after fork from child process 62235] process 62231 is executing new program: /tmp/.mount_krita-LmYq7w/usr/bin/krita [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". NOT COOL: Duplicated action name from xml data: "pickSubwindow" NOT COOL: Duplicated action name from xml data: "openOverview" NOT COOL: Duplicated action name from xml data: "organizerToggle" Bundle "/home/taku/.local/share/krita/Rakurri_Brush_Set_V1.0.bundle" is broken. File "brushes/abominable_snowman.png" is missing Bundle "/home/taku/.local/share/krita/Rakurri_Brush_Set_V.1.1.bundle" is broken. File "paintoppresets/Rakurri_Blender_Frosty.kpp" is missing Bundle "/home/taku/.local/share/krita/Rakurri_Brush_Set_V.1.1.bundle" is broken. File "paintoppresets/Rakurri_Blender_Splatty.kpp" is missing Bundle "/home/taku/.local/share/krita/Rakurri_Brush_Set_V.1.1.bundle" is broken. File "paintoppresets/Rakurri_Pixelblend_Groom.kpp" is missing QObject::startTimer: Timers cannot have negative intervals [Detaching after fork from child process 62246] Could not find platform independent libraries <prefix> Could not find platform dependent libraries <exec_prefix> Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>] /tmp/.mount_krita-LmYq7w/usr/lib/krita-python-libs/krita added to PYTHONPATH QObject::killTimer: Timers cannot be stopped from another thread QObject::~QObject: Timers cannot be stopped from another thread Thread 1 "AppRun" received signal SIGSEGV, Segmentation fault. 0x00007ffff528c484 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /tmp/.mount_krita-LmYq7w/usr/bin/../lib/libQt5Core.so.5 (gdb) STEPS TO REPRODUCE I can't tell because it's not consistent, but I think it might have to do with layer effect luminosity/shine (SAI) OBSERVED RESULT crash SOFTWARE/OS VERSIONS Operating System: Kubuntu 21.10 KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.13.0-30-generic (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 ADDITIONAL INFORMATION
Hey, thanks for the backtrace! I am seeing from the backtrace you are using the recorder docker, could you try and work without that turned on for a while and see if the crash still happens?
(In reply to wolthera from comment #1) > Hey, thanks for the backtrace! > > I am seeing from the backtrace you are using the recorder docker, could you > try and work without that turned on for a while and see if the crash still > happens? not on as in not recording or the actual docker closed? or both
Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information.
The recorder was writing out while the crash happened, but that's not the thread where Krita crashed, that was thread 1, the GUI thread -- but that doesn't show anything relevant because it's in Qt's even handling system.
I'm sorry, but we cannot reproduce the issue which makes it impossible to act on this report: the crash log doesn't give enough information to start debugging.