Bug 412849

Summary:	Crash after deleting layers, resizing image and cropping on relatively large file
Product:	[Applications] krita	Reporter:	Larpon <lp>
Component:	General	Assignee:	Dmitry Kazakov <dimula73>
Status:	RESOLVED FIXED
Severity:	normal	CC:	dimula73, halla
Priority:	NOR
Version First Reported In:	4.2.7
Target Milestone:	---
Platform:	Appimage
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Larpon 2019-10-11 13:03:55 UTC

SUMMARY

1. Window
---
Krita has encountered an internal error:

SAFE ASSERT (krita): "!notifier.isInRecursion()" in file /home/appimage/workspace/Krita_Release_Appimage_Build/krita/libs/ui/input/kis_shortcut_matcher.cpp, line 294

Please report a bug to developers!

Press Ignore to try to continue.
Press Abort to see developers information (all unsaved data will be lost)
---

2. Window
---
Krita has encountered an internal error:

SAFE ASSERT (krita): "m_d->runningShortcut" in file /home/appimage/workspace/Krita_Release_Appimage_Build/krita/libs/ui/input/kis_shortcut_matcher.cpp, line 662

Please report a bug to developers!

Press Ignore to try to continue.
Press Abort to see developers information (all unsaved data will be lost)
---

3. (goes back to 1. and so on ... until you click "abort" instead of "ignore")

STEPS TO REPRODUCE
1. Load image of size 3500x2000
2. Removed 10 layers
3. Resized image via menu to twice the size (3500*2) keep aspect
4. Cropped the image to a smaller size
5. Added new layer
6. Started drawing
7. BOOM

OBSERVED RESULT
Crash

EXPECTED RESULT
No crash

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kubuntu 18.04
KDE Plasma Version: 5.12.9
KDE Frameworks Version: 5.47.0
Qt Version: 5.9.5

ADDITIONAL INFORMATION
I have the 20 megabyte file it happened with - but I can't attach it here

Comment 1 Larpon 2019-10-11 13:17:06 UTC

Reopened as I thought is was the same bug as https://bugs.kde.org/show_bug.cgi?id=412850 - but the messages aren't the same - so I reopened this as well.

Comment 2 Dmitry Kazakov 2019-10-14 12:26:18 UTC

Hi, Larpon!

Could you tell, did you use tablet for doing all these steps? And what tablet device you used?

There was a bug like that on Lenovo Yoga C920 (or C930?) device on Linux, due to some weirdness of the tablet driver...

Comment 3 Larpon 2019-10-15 08:48:41 UTC

Hi Dmitry!

I was using a Wacom Cintiq Companion (1st gen) - so it's using the system installed wacom driver (whatever Kubuntu 18.04 supplies). I haven't had any driver specific problems that I know of with those drivers.

It's often happened that strange things occur when working with "big" files or layers in Krita. I've tried forced shutdowns with similar workflows where "big" files with relatively many layers are manipulated, cropped, resized or moved around - after a short while (after slow operations where Krita, I'm guessing,  reorganizes stuff) - it's become normal that a crash occurs. So my workflow is usually to just save after a "big" operation and restart Krita (I know, it shouldn't be like that :) ). I keep the word big in quotes because it's relatively slow operations on my machine.

Comment 4 Dmitry Kazakov 2019-11-20 13:12:28 UTC

Hi, Lapron!

I have a couple of questions:

1) Do you use a stable build of Krita? If yes, then these asserts should be hidden. Try to use 4.2.7.1, it should have the asserts hidden:
https://download.kde.org/stable/krita/4.2.7.1/

2) I would really like to get a backtrace from this crash. Can you try to get a terminal output/backtrace when pressing Abort in this message box?

Comment 5 Halla Rempt 2022-08-11 10:52:41 UTC

Setting to needsinfo -- though I'm pretty sure it's not relevant anymore (even though the safe assert still exists, we've been working on that file so much since 2019...)

Comment 6 Larpon 2022-08-11 21:21:43 UTC

Yes, sorry I couldn't provide any more details or crash logs at the time. I'm on Kubuntu 20.04 these days and happily using 5.0 now.

Comment 7 Bug Janitor Service 2022-08-12 04:36:01 UTC

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.