Created attachment 127625 [details] system.log is the crash log shown by the OS. SUMMARY This crash looks very different from https://bugs.kde.org/show_bug.cgi?id=420032 so I'm filing a separate report. It happened when I have a selection on the canvas and pressed Cmd+D to deselect it. Krita semi-froze for several seconds. During the period I can select a different layer or switch tools, but the canvas was completely frozen. Then Krita crashed. The stack trace looks different from Bug 420032 too. STEPS TO REPRODUCE Unable to consistently reproduce. OBSERVED RESULT Crash EXPECTED RESULT Not crash, and selection should be deselected. SOFTWARE/OS VERSIONS macOS: 10.14.6 Krita: 4.9.2 ADDITIONAL INFORMATION See attachment
Created attachment 127626 [details] Krita Usage Log, if it matters
I cannot reproduce this issue, i suppose because its random its not that easy to reproduce. Looking at the log provided I can only tell the crash ocurred somewhere at KisSelection::pixelSelection() Are you generate lldb backtraces?
(In reply to vanyossi from comment #2) > I cannot reproduce this issue, i suppose because its random its not that > easy to reproduce. Looking at the log provided I can only tell the crash > ocurred somewhere at KisSelection::pixelSelection() > > Are you generate lldb backtraces? Frankly I don't know how to do that. I tried something like this: > ❯ lldb /Applications/krita.app/Contents/MacOS/krita > (lldb) target create "/Applications/krita.app/Contents/MacOS/krita" > runCurrent executable set to '/Applications/krita.app/Contents/MacOS/krita' (x86_64). > (lldb) run > error: process exited with status -1 (Error 1) But as you can see it doesn't work.
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.
Hi Yu-Hsuan Lai, could you try the lldb steps again with the following dmg? https://drive.google.com/open?id=1xn6eDKG-jPoYqDCdV2mBP2pAVkQcM9dk this one should allow for debugging.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
I've been using 4.3.0-beta1 for a while (30+ hrs) and this hasn't happened. We could probably close this for now.
Thanks for checking!