Created attachment 120712 [details] Safe assert dialog SUMMARY Freeze on safe assert window. Reproducible in 4.2.0, 4.2.1, 4.2.1 from krita plus, current 4.3.0 appimage builds. Works as expected in 4.1.7 in Debug built from git version I can see a lot log messages like this, layer moves after few seconds, but nothing hung: SAFE ASSERT (krita): "stroke" in file /home/dem/kritadev/krita/libs/image/kis_strokes_queue.cpp, line 328 SAFE ASSERT (krita): "m_strokeId" in file /home/dem/kritadev/krita/plugins/tools/basictools/kis_tool_move.cc, line 262 STEPS TO REPRODUCE 1. draw a stroke 2. duplicate layer (Ctrl+J) 3. activate move tool (T) 4. move duplicated layer by keyboard (Shift + ->) OBSERVED RESULT Safe assert dialog appears, No buttons clickable, application froze EXPECTED RESULT Layer moved SOFTWARE/OS VERSIONS Linux: Ubuntu 18.04 ADDITIONAL INFORMATION
Created attachment 120713 [details] screencast
I can't reproduce this one on macOS 4.2.1 This bug could be related to this other bug https://bugs.kde.org/show_bug.cgi?id=408135
Make sure you repeat actions quickly. When I make second-two pause between actions it's not reproducible. For me it's not related to the bug you mentioned.. And cannot reproduce that bug, maybe it's software/hardware specific.
Maybe, but that is still weird. I did tried to reproduce it as shown on the video: blazing fast, but nothing happened. maybe its platform specifyc?
One for Dmitry.
It's possible that HIDE_SAFE_ASSERTS define is inverted under Linux builds? Because I don't have any error message on safe assert when start from compiled sources and have one when start downloaded appimage package. I tried it on Mac and Windows. That was the same behavior as in Linux with compiled sources - no safe assert message box, but similar messages in log when started from Terminal (on Mac). Also after activating move tool it doesn't work the first few seconds on all the architectures (while safe assert messages appearing in terminal).
Created attachment 120823 [details] Log under Mac OS X
*** This bug has been marked as a duplicate of bug 408593 ***