Bug 408474

Summary: Freeze on safe assert "stroke"
Product: [Applications] krita Reporter: Dmitrii Utkin <loentar>
Component: ToolsAssignee: Dmitry Kazakov <dimula73>
Status: RESOLVED DUPLICATE    
Severity: crash CC: ghevan, halla
Priority: NOR    
Version: 4.2.1   
Target Milestone: ---   
Platform: Appimage   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Safe assert dialog
screencast
Log under Mac OS X

Description Dmitrii Utkin 2019-06-09 08:03:05 UTC
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
Comment 1 Dmitrii Utkin 2019-06-09 08:03:46 UTC
Created attachment 120713 [details]
screencast
Comment 2 vanyossi 2019-06-11 04:36:42 UTC
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
Comment 3 Dmitrii Utkin 2019-06-11 12:26:52 UTC
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.
Comment 4 vanyossi 2019-06-11 16:12:29 UTC
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?
Comment 5 Halla Rempt 2019-06-12 13:49:42 UTC
One for Dmitry.
Comment 6 Dmitrii Utkin 2019-06-12 19:03:01 UTC
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).
Comment 7 Dmitrii Utkin 2019-06-12 19:04:13 UTC
Created attachment 120823 [details]
Log under Mac OS X
Comment 8 Dmitry Kazakov 2019-06-13 14:16:22 UTC

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