Created attachment 130459 [details] Krita Crash Log SUMMARY Crash after moving layer and selecting transform tool STEPS TO REPRODUCE 1. Duplicated Layer 2. Moved layer content to the right 3. Selected Transform tool OBSERVED RESULT Hard crash to desktop EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
I don't see this with the Windows 4.3.0 64-bit portable .zip package on Windows 10. Can you do Help -> Show system information for bug reports then paste the output here (or attach a .txt file)? Can you also do Help -> Show Krita log for bug reports and examine it. This may have lots of content but you can copy/paste just the section for the session(s) that had the crash
Created attachment 130466 [details] Output of: Help -> Show system information for bug reports
Created attachment 130467 [details] Output of: Help -> Show Krita log for bug reports (27th and 28th) I made sure that the time frame for the event is inside this document, including a snippet of before and after.
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.
The system information doesn't include Harware Information, Current Settings or Display Information. Could you provide those? Can you replicate this crash with a new simple file? Can you replicate the crash with the file you were using at the time while performing the actions you were doing at the time?
Created attachment 130489 [details] Krita SysInfo File (HW Info, Current Settings, Display Info) I haven't had luck with replicating the crash thus far, with a simple file or the same file.
I was wondering about RAM limit issues among other things but I can see that shouldn't be a problem for you. If it can't be replicated then it can't be investigated but you do have one crash log. All you can do is wait to see if someome else can think of something. Please add any more information if it becomes available. If nothing is added for 30 days then the bug report will be automatically set to Resolved.
I cannot reproduce the problem :( I tried to reproduce the crash by emulating memory corruption, but still couldn't get the same backtrace. It looks like some pointer gets value 0x0000000100000000, and then one of its members with offset 0x20 is read. But it is neither (MoveStrokeStrategy*)this, nor KisStrokeStrategyUndoCommandBased::m_macroCommand. Both of them give different offsets.
Well, I have recently changed the transform tool significantly, so this problem might have been fixed. Since noone could reproduce this problem, I guess I should close this report now. If the problem still appears in Krita 5.0, please reopen the bug.