Bug 380246 - Krita SegFaults and Crashes - Reported "There must be an inconsistency in the walkers happened!"
Summary: Krita SegFaults and Crashes - Reported "There must be an inconsistency in the...
Status: RESOLVED WORKSFORME
Alias: None
Product: krita
Classification: Applications
Component: General (show other bugs)
Version: 3.1.3
Platform: Appimage Linux
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-05-27 07:38 UTC by Cameron Ibrahim
Modified: 2017-11-26 13:30 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
A log of the krita's output following the crash. (19.41 KB, application/pdf)
2017-05-27 07:38 UTC, Cameron Ibrahim 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Cameron Ibrahim 2017-05-27 07:38:54 UTC 
Created attachment 105728 [details]
A log of the krita's output following the crash.

While using the lasso selection tool, I accidentally hit Ctrl-X rather than Ctrl-Z. This caused krita to crash, due to a segmentation fault based on the output. It complained first that "The walker hasn't reached the root layer", then that "There must be an inconsistency in the walkers happened!". I have included the output that resulted from the crash.
Comment 1 mvowada 2017-05-28 08:53:40 UTC 
Hi, Cameron, does it happen always in your case?
It seems I'm not able to reproduce this on Ubuntu with Krita 3.1.4 appimage...
Comment 2 Cameron Ibrahim 2017-05-28 10:12:11 UTC 
(In reply to mvowada from comment #1)
> Hi, Cameron, does it happen always in your case?
> It seems I'm not able to reproduce this on Ubuntu with Krita 3.1.4
> appimage...

No. It happened twice in one session, but has not happened since I filled the bug report. I cannot say for certain what I did to cause the crash. Perhaps because I had meant to hit Ctrl-Z, it arises from hitting both Ctrl-Z and Ctrl-X at the same time?
Comment 3 Halla Rempt 2017-11-21 13:48:22 UTC 
*** Bug 386279 has been marked as a duplicate of this bug. ***
Comment 4 Halla Rempt 2017-11-26 13:30:28 UTC 
Hm... If we cannot get that assert (SAFE ASSERT (krita): m_d->lastKnownValue.isNull() || result == m_d->lastKnownValue" in file) to hit again, there isn't much we can do :-(