https://bugs.kde.org/show_bug.cgi?id=406250
Dmitry Kazakov changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=406250
--- Comment #7 from Dmitry Kazakov ---
Okay, I've managed to reproduce the bug. Here it happens on Linux only
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=406250
wolthera changed:
What|Removed |Added
Ever confirmed|0 |1
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=406250
--- Comment #5 from M ---
Created attachment 119321
--> https://bugs.kde.org/attachment.cgi?id=119321=edit
file:///home/snu/gdb output.txt
Here you go, this is everything from the beginning. The backtrace starts at
line 703.
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=406250
wolthera changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=406250
--- Comment #3 from M ---
If you can try the same steps in the pre-alpha with a filter layer instead of a
clone layer (for example color adjustment curves). That seems to hang and crash
for me almost always, too. In 4.1.8 I wasn't able to provoke a
https://bugs.kde.org/show_bug.cgi?id=406250
vanyossi changed:
What|Removed |Added
CC||ghe...@gmail.com
--- Comment #2 from vanyossi ---
https://bugs.kde.org/show_bug.cgi?id=406250
--- Comment #1 from M ---
And this the last terminal output for 4.1.8:
ASSERT (krita): "0 && "sanity check failed: the tile has already been
removed!"" in file
/build/krita/src/krita-4.1.8/libs/image/tiles3/KisTiledExtentManager.cpp, line
53
Aborted
